linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Henzl <thenzl@redhat.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: nick.cheng@areca.com.tw, linux-scsi@vger.kernel.org,
	James.Bottomley@HansenPartnership.com
Subject: Re: [PATCH 2/2] arcmsr: code cleanup and some corrections
Date: Fri, 18 Feb 2011 11:59:58 +0100	[thread overview]
Message-ID: <4D5E512E.6000904@redhat.com> (raw)
In-Reply-To: <20110218100400A.fujita.tomonori@lab.ntt.co.jp>

On 02/18/2011 02:04 AM, FUJITA Tomonori wrote:
> On Thu, 17 Feb 2011 16:05:37 +0100
> Tomas Henzl <thenzl@redhat.com> wrote:
>
>   
>> the discussion is mostly if 'dma_alloc_coherent' 
>> ...
>> dma_coherent = dma_alloc_coherent(&pdev->dev, acb->uncache_size, &dma_coherent_handle, GFP_KERNEL);
>> ...
>> returns a page address - dma_coherent with last, I think five bits, zeroed.
>> Could you help us with that?
>>     
> Documentation/DMA-API-HOWTO.txt is not clear enough?
>
> =
> dma_alloc_coherent returns two values: the virtual address which you
> can use to access it from the CPU and dma_handle which you pass to the
> card.
>
> The cpu return address and the DMA bus master address are both
> guaranteed to be aligned to the smallest PAGE_SIZE order which
> is greater than or equal to the requested size.  This invariant
> exists (for example) to guarantee that if you allocate a chunk
> which is smaller than or equal to 64 kilobytes, the extent of the
> buffer you receive will not cross a 64K boundary.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   
It's clear enough I think, I asked this question because Nick doesn't
have a "100% confidence in that.". So I wanted a help to convince him.


  reply	other threads:[~2011-02-18 11:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 14:22 [PATCH 1/2] arcmsr: code cleanup and some corrections Tomas Henzl
2011-02-10 14:36 ` [PATCH 2/2] " Tomas Henzl
2011-02-11  1:44   ` NickCheng
2011-02-17 15:05     ` Tomas Henzl
2011-02-18  1:04       ` FUJITA Tomonori
2011-02-18 10:59         ` Tomas Henzl [this message]
2011-02-24 14:14           ` Tomas Henzl
2011-02-25  1:30             ` NickCheng
2011-02-17 15:07 ` [PATCH 1/2] " Tomas Henzl
2011-02-18  1:26   ` NickCheng
2011-02-18 11:04     ` Tomas Henzl
2011-02-18 11:36       ` NickCheng
2011-02-24  2:02   ` NickCheng
2011-02-24 14:09     ` Tomas Henzl
2011-02-25  1:30       ` NickCheng

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=4D5E512E.6000904@redhat.com \
    --to=thenzl@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nick.cheng@areca.com.tw \
    /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).