From: "William J. Earl" <wje@fir.engr.sgi.com>
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: greg@xtp.engr.sgi.com (Greg Chesson),
adevries@engsoc.carleton.ca, anubis@BanjaLuka.NET,
linux@cthulhu.engr.sgi.com
Subject: Re: What about...
Date: Fri, 17 Jul 1998 11:21:18 -0700 [thread overview]
Message-ID: <199807171821.LAA12337@fir.engr.sgi.com> (raw)
In-Reply-To: <m0yxF1A-000aOoC@the-village.bc.nu>
Alan Cox writes:
> > many "holes"... The idea of a simple buddy-system allocator as is
> > ingrained in the Linux kernel falls apart completely in the face of
> > this kind of architecture. I suppose you could run a copy of Linux
> > on every node, but I consider that an excuse rather than a solution.
>
> Actually the Linux buddy stuff is quite happy with holes. Its still
> completely inappropriate. From the above I deduce we'd have to do
> mips64 before we even considerd it anyway
Yes, the address space is very large, even in a single rack.
WARNING: multiple messages have this Message-ID (diff)
From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Greg Chesson <greg@xtp.engr.sgi.com>,
adevries@engsoc.carleton.ca, anubis@BanjaLuka.NET,
linux@cthulhu.engr.sgi.com
Subject: Re: What about...
Date: Fri, 17 Jul 1998 11:21:18 -0700 [thread overview]
Message-ID: <199807171821.LAA12337@fir.engr.sgi.com> (raw)
Message-ID: <19980717182118.8OzbApbdIT4QfTqh3unkkbMfXKePrRUv-reD0c42bck@z> (raw)
In-Reply-To: <m0yxF1A-000aOoC@the-village.bc.nu>
Alan Cox writes:
> > many "holes"... The idea of a simple buddy-system allocator as is
> > ingrained in the Linux kernel falls apart completely in the face of
> > this kind of architecture. I suppose you could run a copy of Linux
> > on every node, but I consider that an excuse rather than a solution.
>
> Actually the Linux buddy stuff is quite happy with holes. Its still
> completely inappropriate. From the above I deduce we'd have to do
> mips64 before we even considerd it anyway
Yes, the address space is very large, even in a single rack.
next prev parent reply other threads:[~1998-07-17 18:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <35ADF6D0.46FCB21E@BanjaLuka.NET>
1998-07-17 5:24 ` What about Alex deVries
1998-07-17 5:30 ` Greg Chesson
1998-07-17 14:11 ` William J. Earl
1998-07-17 15:07 ` Alan Cox
1998-07-17 15:07 ` Alan Cox
1998-07-17 17:43 ` ralf
1998-07-17 17:53 ` Alan Cox
1998-07-17 22:15 ` Jeffrey Watts
1998-07-17 17:29 ` ralf
1998-07-17 18:01 ` Greg Chesson
1998-07-17 18:19 ` William J. Earl
1998-07-18 1:57 ` ralf
1998-07-18 2:00 ` Greg Chesson
[not found] ` <wje@fir>
1998-07-17 17:47 ` Greg Chesson
1998-07-17 18:14 ` Alan Cox
1998-07-17 18:14 ` Alan Cox
1998-07-17 18:21 ` William J. Earl [this message]
1998-07-17 18:21 ` William J. Earl
1998-07-18 1:37 ` ralf
1998-07-18 1:58 ` Greg Chesson
1998-07-18 2:44 ` ralf
1998-07-18 10:47 ` ralf
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=199807171821.LAA12337@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=adevries@engsoc.carleton.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=anubis@BanjaLuka.NET \
--cc=greg@xtp.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
/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