[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z-AbwwTtfpKr_pgY@casper.infradead.org>
Date: Sun, 23 Mar 2025 14:33:39 +0000
From: Matthew Wilcox <willy@...radead.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: David Howells <dhowells@...hat.com>,
Leon Romanovsky <leonro@...dia.com>,
Christian Brauner <christian@...uner.io>,
Chuck Lever <chuck.lever@...cle.com>,
Steve French <smfrench@...il.com>,
Ilya Dryomov <idryomov@...il.com>, netfs@...ts.linux.dev,
linux-fsdevel@...r.kernel.org, linux-block@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/4] iov_iter: Add composite, scatterlist and skbuff
iterator types
On Sat, Mar 22, 2025 at 11:21:28PM -0700, Christoph Hellwig wrote:
> This is going entirely in the wrong direction. We don't need more iter
> types but less. The reason why we have to many is because the underlying
> representation of the ranges is a mess which goes deeper than just the
> iterator, because it also means we have to convert between the
> underlying representations all the time.
>
> E.g. the socket code should have (and either has for a while or at least
> there were patches) been using bio_vecs instead of reinventing them as sk
> fragment. The crypto code should not be using scatterlists, which are a
I did this work six years ago -- see 8842d285bafa
Unfortunately, networking is full of inconsiderate arseholes who backed
it out without even talking to me in 21d2e6737c97
Powered by blists - more mailing lists