linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>, David Howells <dhowells@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org,
	Matthew Wilcox <willy@infradead.org>,
	brauner@kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
	linux-fsdevel@vger.kernel.org, linux-crypto@vger.kernel.org,
	linux-mm@kvack.org, linux-block@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>, Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [LSF/MM/BPF TOPIC] Improving iov_iter - and replacing scatterlists
Date: Mon, 20 Jan 2025 11:03:22 -0800	[thread overview]
Message-ID: <60a88ff2-bc03-405f-8a26-3808774dfd6a@nvidia.com> (raw)
In-Reply-To: <20250120142217.GA153811@unreal>



On 1/20/25 6:22 AM, Leon Romanovsky wrote:
> On Fri, Jan 17, 2025 at 09:16:52PM +0000, David Howells wrote:
>> Hi,
>>
>> I'd like to propose a discussion of two things: firstly, how might we improve
>> iov_iter and, secondly, would it be possible to replace scatterlists.
> 
> <...>
> 
>> Rumour has it that John Hubbard may be working along similar lines, possibly
>> just in the area of bio_vecs and ITER_BVEC.

I do feel the need to apologize to Leon here, because I've been mostly MIA
ever we talked about this at LPC. Perhaps I'll actually be of some use in
2025. :)

>>
>>
>> [*] Second: Can we replace the uses of scatterlist with iov_iter and reduce
>> the number of iterator classes we have?
> 
> <...>
> 
> I would say yes to the questions.
> 
> Regarding rumors, I don't know, but Christoph, Jason and I are working towards
> this goal. We proposed new DMA API which doesn't need scatterlists and allows
> callers to implement their own data-structures.
> 
> See this "[PATCH v6 00/17] Provide a new two step DMA mapping API" series
> https://lore.kernel.org/all/cover.1737106761.git.leon@kernel.org
> and its block layer followup "[RFC PATCH 0/7] Block and NMMe PCI use of
> new DMA mapping API"
> https://lore.kernel.org/all/cover.1730037261.git.leon@kernel.org
> 
> Thanks

thanks,
-- 
John Hubbard



  reply	other threads:[~2025-01-20 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17 21:16 David Howells
2025-01-20 14:22 ` Leon Romanovsky
2025-01-20 19:03   ` John Hubbard [this message]
2025-01-31 16:08 ` Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60a88ff2-bc03-405f-8a26-3808774dfd6a@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jgg@nvidia.com \
    --cc=leon@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox