Thread (21 messages) 21 messages, 6 authors, 2017-03-24

Re: [PATCH 3/8] nowait aio: return if direct write will trigger writeback

From: Goldwyn Rodrigues <hidden>
Date: 2017-03-16 13:46:35
Also in: linux-api, linux-btrfs, linux-ext4, linux-fsdevel, linux-xfs


On 03/16/2017 08:08 AM, Matthew Wilcox wrote:
On Wed, Mar 15, 2017 at 04:51:02PM -0500, Goldwyn Rodrigues wrote:
quoted
This introduces a new function filemap_range_has_page() which
returns true if the file's mapping has a page within the range
mentioned.
I thought you were going to replace this patch with one that starts
writeback for these pages but does not wait for them?
As mentioned by Jan, Flags to filemap_write_and_wait_range are
unnecessarily complicated. The AIO-DIO API users who eye for performance
usually are careful with page writes/evictions. As a fallback, they can
(and should) go the wait route (without  IOCB_RW_FLAG_NOWAIT).

Finally, my take on this is that we don't want to perform tasks for a
following system call, which may or may not immediately follow the
current one. May not, because an application (DB) will offload the task
from the CPU thread to the I/O thread in case of -EAGAIN. A system call
should be complete in itself (and do the minimum, what is asked).


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