mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Cameron@laptop.fenrus.com, Steve <Steve.Cameron@hp.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [Fwd: RE: cciss patches for 2.4.21-rc1, 4 of 4]
Date: 25 Apr 2003 16:29:15 +0200	[thread overview]
Message-ID: <1051280955.1391.21.camel@laptop.fenrus.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 971 bytes --]

-----Forwarded Message-----

> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
> To: "Miller, Mike (OS Dev)" <Mike.Miller@hp.com>
> Cc: "Cameron, Steve" <Steve.Cameron@hp.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
> Subject: RE: cciss patches for 2.4.21-rc1, 4 of 4
> Date: 25 Apr 2003 14:09:53 +0100
> 
> On Gwe, 2003-04-25 at 14:48, Miller, Mike (OS Dev) wrote:
> > I haven't seen any issues (yet) on ia64. I'm running with 5GB RAM.
> 
> That doesn't make it correct. This same problem occurs in other drivers
> and the usual trick is to set the pci mask to 32bit, allocate those
> command buffers ready, then flip back to 64bit. Just be sure one thread
> doesn't change it to 64bit while another is allocating commands. The
> reverse is fine since an accidental odd bounce is no big deal
Alan,

except that pci_alloc_consistent is guaranteed to return a 32 bit address

what you're thinking about is the mapping interface instead.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2003-04-25 14:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1051280955.1391.21.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=Cameron@laptop.fenrus.com \
    --cc=Steve.Cameron@hp.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®