mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jmerkey@timpanogas.org, linux-kernel@vger.kernel.org
Subject: Re: bigphysarea support in 2.2.19 and 2.4.0 kernels
Date: Thu, 21 Dec 2000 15:44:46 -0700	[thread overview]
Message-ID: <20001221154446.A10579@vger.timpanogas.org> (raw)
In-Reply-To: <20001221144247.A10273@vger.timpanogas.org> <E149DKS-0003cX-00@the-village.bc.nu>
In-Reply-To: <E149DKS-0003cX-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Dec 21, 2000 at 09:32:46PM +0000

On Thu, Dec 21, 2000 at 09:32:46PM +0000, Alan Cox wrote:
> > A question related to bigphysarea support in the native Linux
> > 2.2.19 and 2.4.0 kernels.
> > 
> > I know there are patches for this support, but is it planned for 
> > rolling into the kernel by default to support Dolphin SCI and 
> > some of the NUMA Clustering adapters.  I see it there for some 
> > of the video adapters.
> 
> bigphysarea is the wrong model for 2.4. The bootmem allocator means that
> drivers could do early claims via the bootmem interface during boot up. That
> would avoid all the cruft.
> 
> For 2.2 bigphysarea is a hack, but a neccessary add on patch and not one you
> can redo cleanly as we don't have bootmem
> 
> I belive Pauline Middelink had a patch implementing bigphysarea in terms of
> bootmem
> 
> Alan

Alan,

Thanks for the prompt response.  I am merging the Dolphin SCI High Speed
interconnect drivers into 2.2.18 and 2.4.0 for our M2FS project, and I 
am reviewing the big ugly nasty patch they have current as of 2.2.13 
(really old).  I will be looking over the 2.4 tree for a more clean 
manner to do what they want.

What's in the patch alters the /proc filesystem, and the VM code.  I will
submit a patch against 2.2.19 and 2.4.0 for this support for their SCI 
adapters after I get a handle on it.

:-)

Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-21 22:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-21 21:42 Jeff V. Merkey
2000-12-21 21:32 ` Alan Cox
2000-12-21 22:44   ` Jeff V. Merkey [this message]
2000-12-21 22:53     ` Jeff V. Merkey
2000-12-22  8:39       ` Pauline Middelink
2000-12-22  8:58         ` Alan Cox
2000-12-22 23:11           ` Albert D. Cahalan
2000-12-23  8:40             ` Eric W. Biederman
2000-12-24  8:59               ` Albert D. Cahalan
2000-12-23 20:11             ` Jes Sorensen
2000-12-24  8:15               ` Albert D. Cahalan
2000-12-22 18:11         ` Jeff V. Merkey
2000-12-22 18:35           ` Jeff V. Merkey
2000-12-22 19:21             ` Andi Kleen
2000-12-22 20:25               ` Jeff V. Merkey
2000-12-22 19:51                 ` Pauline Middelink
2000-12-22 21:54                   ` Jeff V. Merkey
2000-12-22 21:39                     ` Erik Mouw
2000-12-22 23:56                       ` Jeff V. Merkey
2000-12-22 19:37           ` NUMA and SCI [was Re: bigphysarea support in 2.2.19 and 2.4.0 kernels] Tim Wright
2000-12-22 20:39             ` Jeff V. Merkey
2000-12-22 20:30               ` Alan Cox
2000-12-22 21:40                 ` Jeff V. Merkey
2000-12-22 21:52                   ` Jeff V. Merkey

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=20001221154446.A10579@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jmerkey@timpanogas.org \
    --cc=linux-kernel@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

Powered by JetHome