From: Jeremy Higdon <jeremy@sgi.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
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 23:39:00 +0000 [thread overview]
Message-ID: <20040213233900.GE504054@sgi.com> (raw)
In-Reply-To: <20040213231308.GT31168@parcelfarce.linux.theplanet.co.uk>
On Fri, Feb 13, 2004 at 11:13:08PM +0000, Matthew Wilcox wrote:
> On Fri, Feb 13, 2004 at 03:52:43PM -0700, Bjorn Helgaas wrote:
> > > 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?
>
> Since we use buddy allocators everywhere, we'd need to be doing 8GB
> allocations to cross a 4GB barrier. Of course if we change allocators ...
... and this particular behavior, then I think lots of hardware will
stop working, because LSI is not the only vendor with this sort of
limitation :-)
jeremy
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Higdon <jeremy@sgi.com>
To: Matthew Wilcox <willy@debian.org>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
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:39:00 -0800 [thread overview]
Message-ID: <20040213233900.GE504054@sgi.com> (raw)
In-Reply-To: <20040213231308.GT31168@parcelfarce.linux.theplanet.co.uk>
On Fri, Feb 13, 2004 at 11:13:08PM +0000, Matthew Wilcox wrote:
> On Fri, Feb 13, 2004 at 03:52:43PM -0700, Bjorn Helgaas wrote:
> > > 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?
>
> Since we use buddy allocators everywhere, we'd need to be doing 8GB
> allocations to cross a 4GB barrier. Of course if we change allocators ...
... and this particular behavior, then I think lots of hardware will
stop working, because LSI is not the only vendor with this sort of
limitation :-)
jeremy
next prev parent reply other threads:[~2004-02-13 23:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 16:12 mpt sets 64bit consistent mask yet requires mapping in same 4GB Alex Williamson
2004-02-13 16:12 ` mpt sets 64bit consistent mask yet requires mapping in same 4GB chunk?!? Alex Williamson
2004-02-13 21:20 ` mpt sets 64bit consistent mask yet requires mapping in same 4 Moore, Eric Dean
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 21:30 ` Jesse Barnes
2004-02-13 22:52 ` Bjorn Helgaas
2004-02-13 22:52 ` Bjorn Helgaas
2004-02-13 23:08 ` Jeremy Higdon
2004-02-13 23:08 ` Jeremy Higdon
2004-02-13 23:13 ` Matthew Wilcox
2004-02-13 23:39 ` Jeremy Higdon [this message]
2004-02-13 23:39 ` Jeremy Higdon
2004-02-13 23:23 ` mpt sets 64bit consistent mask yet requires mapping in same 4 Moore, Eric Dean
2004-02-13 23:23 ` mpt sets 64bit consistent mask yet requires mapping in same 4 GB chunk?!? Moore, Eric Dean
-- strict thread matches above, loose matches on Subject: below --
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=20040213233900.GE504054@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 \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.