Thread (20 messages) 20 messages, 3 authors, 2013-08-12

Re: [RFC 0/3] Add madvise(..., MADV_WILLWRITE)

From: Andy Lutomirski <luto@amacapital.net>
Date: 2013-08-07 18:01:15
Also in: linux-mm, lkml

On Wed, Aug 7, 2013 at 10:40 AM, Dave Hansen [off-list ref] wrote:
On 08/07/2013 06:40 AM, Jan Kara wrote:
quoted
  One question before I look at the patches: Why don't you use fallocate()
in your application? The functionality you require seems to be pretty
similar to it - writing to an already allocated block is usually quick.
One problem I've seen is that it still costs you a fault per-page to get
the PTEs in to a state where you can write to the memory.  MADV_WILLNEED
will do readahead to get the page cache filled, but it still leaves the
pages unmapped.  Those faults get expensive when you're trying to do a
couple hundred million of them all at once.
I have grand plans to teach the kernel to use hardware dirty tracking
so that (some?) pages can be left clean and writable for long periods
of time.  This will be hard.

Even so, the second write fault to a page tends to take only a few
microseconds, while the first one often blocks in fs code.

(mmap_sem is a different story, but I see it as a separate issue.)

--Andy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help