From: James Bottomley <James.Bottomley@steeleye.com>
To: Andi Kleen <ak@muc.de>, Eric Dean Moore <Emoore@lsil.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [BK PATCH] essential SCSI fixes for 2.6.5-rc2
Date: 20 Mar 2004 10:21:06 -0500 [thread overview]
Message-ID: <1079796067.1755.18.camel@mulgrave> (raw)
In-Reply-To: <m3u10jr93e.fsf@averell.firstfloor.org>
On Sat, 2004-03-20 at 07:33, Andi Kleen wrote:
> Any chance you could include the fusion consistent mask patch with this?
>
> Without this fusion is completely unusable with >4GB on 64bit.
But if I include this patch, it will break Altix.
Eric, could you make fixing this your top priority? Even if you can't
consolidate the allocations, what about using dma_pool instead?
James
> diff -burpN -X ../KDIFX -x '*-SLAB' linux-vanilla-2.6.5rc2/drivers/message/fusion/mptbase.c linux-2.6.5rc2-amd64/drivers/message/fusion/mptbase.c
> --- linux-vanilla-2.6.5rc2/drivers/message/fusion/mptbase.c 2004-03-20 03:55:31.000000000 +0100
> +++ linux-2.6.5rc2-amd64/drivers/message/fusion/mptbase.c 2004-03-20 04:11:24.000000000 +0100
> @@ -1280,12 +1280,17 @@ mptbase_probe(struct pci_dev *pdev, cons
> return r;
> }
>
> +#if 0
> + /* broken because some code assumes that multiple calls
> + to pci_alloc_consistent return data in the same 4GB segment.
> + This cannot work on machines with enough memory. */
> if (!pci_set_consistent_dma_mask(pdev, mask))
> dprintk((KERN_INFO MYNAM
> ": Using 64 bit consistent mask\n"));
> else
> dprintk((KERN_INFO MYNAM
> ": Not using 64 bit consistent mask\n"));
> +#endif
>
> ioc = kmalloc(sizeof(MPT_ADAPTER), GFP_ATOMIC);
> if (ioc == NULL) {
next prev parent reply other threads:[~2004-03-20 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 14:30 [BK PATCH] essential SCSI fixes for 2.6.5-rc2 James Bottomley
2004-03-20 12:33 ` Andi Kleen
2004-03-20 15:21 ` James Bottomley [this message]
2004-03-21 5:26 ` Moore, Eric Dean
2004-03-21 4:36 ` Andi Kleen
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=1079796067.1755.18.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Emoore@lsil.com \
--cc=ak@muc.de \
--cc=linux-scsi@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