From: Alex Williamson <alex.williamson@hp.com>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: jbarnes@sgi.com, jeremy@sgi.com, bjorn.helgaas@hp.com,
willy@debian.org, James.Bottomley@steeleye.com,
linux-scsi@vger.kernel.org
Subject: RE: mpt sets 64bit consistent mask yet requires mapping in same 4 GB chunk?!?
Date: Wed, 18 Feb 2004 11:52:57 -0700 [thread overview]
Message-ID: <1077130375.3066.17.camel@patsy.fc.hp.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E5703EF9372@exa-atlanta.se.lsil.com>
On Wed, 2004-02-18 at 11:41, Moore, Eric Dean wrote:
> Regarding last weeks thread
> on mpt fusion driver(2.6 kernel), and PrimeIocFifos:
>
[snip... a third allocation dependency]
> If this fix is urgent, I recommend providing a quick
> fix which is creating 32bit pci_dev mask just for these
> three pci_alloc_consistent calls.
>
The current failure mode is pretty ugly and appears fairly random. I
would consider getting something that works reliably to be urgent. It
sounds easy and safe to twiddle the consistent device mask in the short
term and combine these allocations in a future rev. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2004-02-18 18:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 18:41 mpt sets 64bit consistent mask yet requires mapping in same 4 GB chunk?!? Moore, Eric Dean
2004-02-18 18:52 ` Alex Williamson [this message]
2004-02-18 23:20 ` Jeremy Higdon
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 17:18 Moore, Eric Dean
2004-02-20 6:30 ` Jeremy Higdon
2004-02-19 0:03 Moore, Eric Dean
2004-02-19 1:09 ` Jeremy Higdon
2004-02-13 23:23 Moore, Eric Dean
2004-02-13 21:20 Moore, Eric Dean
2004-02-13 21:30 ` Jesse Barnes
2004-02-13 22:52 ` Bjorn Helgaas
2004-02-13 23:08 ` Jeremy Higdon
2004-02-13 23:13 ` Matthew Wilcox
2004-02-13 23:39 ` Jeremy Higdon
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=1077130375.3066.17.camel@patsy.fc.hp.com \
--to=alex.williamson@hp.com \
--cc=Emoore@lsil.com \
--cc=James.Bottomley@steeleye.com \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@sgi.com \
--cc=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@debian.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