public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Higdon <jeremy@sgi.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesse Barnes <jbarnes@sgi.com>,
	"Moore, Eric Dean" <Emoore@lsil.com>,
	Alex Williamson <alex.williamson@hp.com>,
	linux-scsi@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: mpt sets 64bit consistent mask yet requires mapping in same 4 GB chunk?!?
Date: Fri, 13 Feb 2004 15:08:09 -0800	[thread overview]
Message-ID: <20040213230809.GB504054@sgi.com> (raw)
In-Reply-To: <200402131552.43935.bjorn.helgaas@hp.com>

On Fri, Feb 13, 2004 at 03:52:43PM -0700, Bjorn Helgaas wrote:
> On Friday 13 February 2004 2:30 pm, Jesse Barnes wrote:
> > On Fri, Feb 13, 2004 at 04:20:35PM -0500, Moore, Eric Dean wrote:
> > > I added pci_set_consistent_dma_mask() per request from
> > > Jeremy Higdon<jeremy@sgi.com> back on 12/03/03. He
> > > was having problems on a Altix (IA64) system. See
> > > attached email.  What is your recommendation? I have a mpt 
> > > patch in the queue which doesn't address this.
> > > 
> > > On Friday, February 13, 2004 9:12 AM, Alex Williamson wrote:
> > > > These are two perfectly valid consistent mappings as far as the
> > > > platform code is concerned.  I think mpt really needs to either set
> > > > a 32bit consistent map of do a single allocation when it requires
> > > > this type of thing.  Thanks,
> > 
> > I think Alex's second suggestion would be the best--do a single
> > allocation rather than falling back to a 32 bit consistent mask.
> 
> But even with a single allocation, there's nothing to prevent it
> from crossing a 4GB boundary, is there?

I don't think the Linux memory allocator will give back memory that
crosses a 32 bit boundary.

But I'm not an expert.  If I'm wrong, hopefully an expert will chime
in  :-)

jeremy

  reply	other threads:[~2004-02-13 23:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 21:20 mpt sets 64bit consistent mask yet requires mapping in same 4 GB chunk?!? Moore, Eric Dean
2004-02-13 21:30 ` Jesse Barnes
2004-02-13 22:52   ` Bjorn Helgaas
2004-02-13 23:08     ` Jeremy Higdon [this message]
2004-02-13 23:13     ` Matthew Wilcox
2004-02-13 23:39       ` Jeremy Higdon
  -- strict thread matches above, loose matches on Subject: below --
2004-02-13 23:23 Moore, Eric Dean
2004-02-18 18:41 Moore, Eric Dean
2004-02-18 18:52 ` Alex Williamson
2004-02-18 23:20   ` Jeremy Higdon
2004-02-19  0:03 Moore, Eric Dean
2004-02-19  1:09 ` Jeremy Higdon
2004-02-19 17:18 Moore, Eric Dean
2004-02-20  6:30 ` 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=20040213230809.GB504054@sgi.com \
    --to=jeremy@sgi.com \
    --cc=Emoore@lsil.com \
    --cc=alex.williamson@hp.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=jbarnes@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --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