From: Arjan van de Ven <arjanv@redhat.com>
To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
Cc: "Cameron, Steve" <Steve.Cameron@hp.com>,
linux-kernel@vger.kernel.org, davem@redhat.com
Subject: RE: cciss patches for 2.4.21-rc1, 4 of 4
Date: 25 Apr 2003 16:06:05 +0200 [thread overview]
Message-ID: <1051279564.1391.18.camel@laptop.fenrus.com> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF1040528C8@cceexc23.americas.cpqcorp.net>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
On Fri, 2003-04-25 at 15:48, Miller, Mike (OS Dev) wrote:
> I haven't seen any issues (yet) on ia64. I'm running with 5GB RAM.
>
> mikem
>
> -----Original Message-----
> From: Cameron, Steve
> Sent: Friday, April 25, 2003 8:25 AM
> Cc: linux-kernel@vger.kernel.org; Miller, Mike (OS Dev)
> Subject: RE: cciss patches for 2.4.21-rc1, 4 of 4
>
>
>
> Mike Miller wrote:
>
> > Changes:
> > 1. Sets the DMA mask to 64 bits. Removes RH's code for the DMA mask.
>
> In order for this to work, it depends on pci_alloc_consistent always
> returning memory with physical addresses that fit in 32 bits,
> regardless of the DMA mask, since the cciss device's command register
> is 32 bits, and the command buffer addresses must fit in there. If
> that's the case, this is fine. Otherwise, this may fail if pci_alloc_consistent
> returns memory above 4GB. (on x86, I think this is not a problem, not
> sure of other archs, e.g. alpha, ia64)
Cameron, lots of people told you numerous times that pci_alloc_consitent
is guaranteed to return 32 bit addresses by the API, see
Documentation/DMA-mapping.txt for the API definition.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-25 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 13:48 Miller, Mike (OS Dev)
2003-04-25 13:09 ` Alan Cox
2003-04-25 14:06 ` Arjan van de Ven [this message]
2003-04-25 14:50 Cameron, Steve
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=1051279564.1391.18.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=Mike.Miller@hp.com \
--cc=Steve.Cameron@hp.com \
--cc=davem@redhat.com \
--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®