lkml.org 
[lkml]   [2013]   [Aug]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH V8 00/33] loop: Issue O_DIRECT aio using bio_vec
On Wed, 21 Aug 2013 09:02:31 -0400 Benjamin LaHaise <bcrl@kvack.org> wrote:

> One of the major problems your changeset continues to carry is that your
> new read_iter/write_iter operations permit blocking (implicitely), which
> really isn't what we want for aio. If you're going to introduce a new api,
> it should be made non-blocking, and enforce that non-blocking requirement

It's been so incredibly long and I've forgotten everything AIO :(

In this context, "non-blocking" means no synchronous IO, yes? Even for
indirect blocks, etc. What about accidental D-state blockage in page
reclaim, or against random sleeping locks?

Also, why does this requirement exist? "99% async" is not good enough?
How come?



\
 
 \ /
  Last update: 2013-08-21 22:01    [W:0.310 / U:0.228 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site