From: 'Christoph Hellwig' <hch@infradead.org>
To: "Bagalkote, Sreenivas" <sreenib@lsil.com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
'Arjan van de Ven' <arjan@infradead.org>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
'James Bottomley' <James.Bottomley@SteelEye.com>,
"'Matt_Domsch@Dell.com'" <Matt_Domsch@Dell.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [ANNOUNCE][PATCH 2.6.11 2/3] megaraid_sas: Announcing new mod ule for LSI Logic's SAS based MegaRAID controllers
Date: Wed, 9 Mar 2005 22:59:27 +0000 [thread overview]
Message-ID: <20050309225927.GA10646@infradead.org> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E570230CC22@exa-atlanta>
On Wed, Mar 09, 2005 at 05:47:27PM -0500, Bagalkote, Sreenivas wrote:
> >
> >Even for kernels with a 64bit dma_addr_t you can get 32bit dma
> >addresses
> >only. As a start check whether the pci_set_dma_mask for the 64bit mask
> >failed - in that case you can always use 32bit SGLs.
> >
>
> Please help me understand: If dma_addr_t is 64 bit, I will get 64bit
> addresses in scatterlist regardless the outcome of pci_set_dma_mask,
> won't I? These addresses may have valid or null high addresses. My idea
> was to have 32(64) bit SGLs for 32(64) bit dma_addr_t.
if pci_set_dma_mask for the 64bit mask fails the upper 32bit bit of
dma_addr_t will guaranteed to be zero, so you don't need to take them
into account for your hardware SGL.
next prev parent reply other threads:[~2005-03-09 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 22:47 [ANNOUNCE][PATCH 2.6.11 2/3] megaraid_sas: Announcing new mod ule for LSI Logic's SAS based MegaRAID controllers Bagalkote, Sreenivas
2005-03-09 22:59 ` 'Christoph Hellwig' [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 23:56 Bagalkote, Sreenivas
2005-03-09 17:44 Bagalkote, Sreenivas
2005-03-09 18:19 ` Arjan van de Ven
2005-03-09 16:01 Bagalkote, Sreenivas
2005-03-09 17:16 ` Arjan van de Ven
2005-03-09 14:43 Bagalkote, Sreenivas
2005-03-09 15:52 ` Arjan van de Ven
2005-03-09 22:03 ` 'Christoph Hellwig'
2005-03-08 23:08 Bagalkote, Sreenivas
2005-03-09 8:06 ` Arjan van de Ven
2005-03-08 22:58 Bagalkote, Sreenivas
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=20050309225927.GA10646@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=Matt_Domsch@Dell.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sreenib@lsil.com \
/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