From: Christoph Hellwig <hch@infradead.org>
To: Daniel Drake <drake@endlessm.com>
Cc: jgg@mellanox.com, imre.deak@intel.com,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org,
Oleksij Rempel <linux@rempel-privat.de>
Subject: Re: sg_dma_page_iter offset & length considerations
Date: Thu, 25 Apr 2019 01:02:43 -0700 [thread overview]
Message-ID: <20190425080243.GA10677@infradead.org> (raw)
In-Reply-To: <CAD8Lp47JYdZzbV9F+asNwvSfLF_po_J7ir6R_Vb-Dab21_=Krw@mail.gmail.com>
Given that mmc uses block layer helpers to build the sg list you
just have to set the right block layer and DMA layer (in case an
iommu merges during map_sg) dma_boundary paramters (PAGE_SIZE - 1),
and you should get sglists formatted to your requirements, no need
to use an iterator.
prev parent reply other threads:[~2019-04-25 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 7:22 sg_dma_page_iter offset & length considerations Daniel Drake
2019-04-24 7:57 ` Arnd Bergmann
2019-04-24 11:21 ` Jason Gunthorpe
2019-04-25 7:38 ` Daniel Drake
2019-04-25 8:02 ` Christoph Hellwig [this message]
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=20190425080243.GA10677@infradead.org \
--to=hch@infradead.org \
--cc=drake@endlessm.com \
--cc=imre.deak@intel.com \
--cc=jgg@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux@rempel-privat.de \
/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;
as well as URLs for NNTP newsgroup(s).