From: James Bottomley <James.Bottomley@suse.de>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH -mm 1/4] DMA-API.txt: add dma_sync_single/sg API description
Date: Wed, 03 Feb 2010 21:34:35 -0600 [thread overview]
Message-ID: <1265254475.2873.1716.camel@mulgrave.site> (raw)
In-Reply-To: <20100204123056Q.fujita.tomonori@lab.ntt.co.jp>
On Thu, 2010-02-04 at 12:31 +0900, FUJITA Tomonori wrote:
> On Wed, 03 Feb 2010 19:21:23 -0800 (PST)
> David Miller <davem@davemloft.net> wrote:
>
> > From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> > Date: Thu, 4 Feb 2010 12:13:22 +0900
> >
> > > This adds the description of the following eight function:
> > >
> > > dma_sync_single_for_cpu
> > > pci_dma_sync_single_for_cpuvoid
> > ^^^^
> >
> > That "void" is probably some cut and paste error :-)
>
> Oops.
>
>
> > > dma_sync_single_for_device
> > > pci_dma_sync_single_for_device
> > > dma_sync_sg_for_cpu
> > > pci_dma_sync_sg_for_cpu
> > > dma_sync_sg_for_device
> > > pci_dma_sync_sg_for_device
> > >
> > > It was unclear that the API permits a partial sync (some network
> > > drivers already do though). I made it clear that the sync_single API
> > > can do a partial sync but the sync_sg API can't.
> > >
> > > We could do a partial sync with the sync_sg too, however, it's
> > > difficult for driver writers to correctly use the sync_sg API for a
> > > partial sync since the scatterlists passed in to the mapping API can
> > > be modified. It's unlikely that driver writers want to do a partial
> > > sync with the sync_sg API (because the sync_sg API are usually used
> > > for block drivers). So I think that it's better to forbid a partial
> > > sync with the sync_sg API.
> > >
> > > Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> >
> > Acked-by: David S. Miller <davem@davemloft.net>
>
> Thanks,
>
> I found other two typos in the commit log so here's the update.
>
> =
> From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Subject: [PATCH -mm 1/4] DMA-API.txt: add dma_sync_single/sg API description
>
> This adds the description of the following eight function:
>
> dma_sync_single_for_cpu
> pci_dma_sync_single_for_cpu
> dma_sync_single_for_device
> pci_dma_sync_single_for_device
> dma_sync_sg_for_cpu
> pci_dma_sync_sg_for_cpu
> dma_sync_sg_for_device
> pci_dma_sync_sg_for_device
>
> It was unclear that the API permits a partial sync (some network
> drivers already do though). I made it clear that the sync_single API
> can do a partial sync but the sync_sg API can't.
>
> We could do a partial sync with the sync_sg API too, however, it's
> difficult for driver writers to correctly use the sync_sg API for a
> partial sync since the scatterlists passed in to the mapping API can't
> be modified. It's unlikely that driver writers want to do a partial
> sync with the sync_sg API (because the sync_sg API are usually used
> for block drivers). So I think that it's better to forbid a partial
> sync with the sync_sg API.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Acked-by: David S. Miller <davem@davemloft.net>
> Cc: James Bottomley <James.Bottomley@suse.de>
For what it's worth, you can add my acked by to both patches too.
James
prev parent reply other threads:[~2010-02-04 3:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 3:13 FUJITA Tomonori
2010-02-04 3:13 ` [PATCH -mm 2/4] DMA-API.txt: remove dma_sync_single_range description FUJITA Tomonori
2010-02-04 3:21 ` David Miller
2010-02-04 3:13 ` [PATCH -mm 3/4] alpha: remove dma_sync_single_range FUJITA Tomonori
2010-02-04 3:21 ` David Miller
2010-02-04 4:06 ` Matt Turner
2010-02-04 4:08 ` Andrew Morton
2010-02-04 3:13 ` [PATCH -mm 4/4] um: " FUJITA Tomonori
2010-02-04 3:21 ` David Miller
2010-02-04 3:21 ` [PATCH -mm 1/4] DMA-API.txt: add dma_sync_single/sg API description David Miller
2010-02-04 3:31 ` FUJITA Tomonori
2010-02-04 3:34 ` James Bottomley [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=1265254475.2873.1716.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®