Thread (26 messages) 26 messages, 7 authors, 2020-12-13

Re: [PATCH 1/2] iov: introduce ITER_BVEC_FLAG_FIXED

From: Al Viro <viro@zeniv.linux.org.uk>
Date: 2020-12-09 13:09:00
Also in: io-uring, linux-fsdevel, lkml

On Wed, Dec 09, 2020 at 08:36:45AM +0000, Christoph Hellwig wrote:
This is making the iter type even more of a mess than it already is.
I think we at least need placeholders for 0/1 here and an explicit
flags namespace, preferably after the types.

Then again I'd much prefer if we didn't even add the flag or at best
just add it for a short-term transition and move everyone over to the
new scheme.  Otherwise the amount of different interfaces and supporting
code keeps exploding.
Yes.  The only problem I see is how to describe the rules - "bdev-backed
iterators need the bvec array to stay allocated until IO completes"?
And one way or another, that needs to be documented - D/f/porting with
"mandatory" for priority.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help