public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: john@vnet.ibm.com, LINUX-KERNEL@vger.kernel.org
Subject: Re: Reserving large amounts of RAM for busmastering PCI card.
Date: Wed, 25 Jul 2001 18:05:03 -0400	[thread overview]
Message-ID: <3B5F428F.14DCAA44@mandrakesoft.com> (raw)
In-Reply-To: <mailman.996053899.5490.linux-kernel2news@redhat.com> <200107252200.f6PM0IJ01020@devserv.devel.redhat.com>

Pete Zaitcev wrote:
> 
> >  Since the 2.4 kernels introduce the e820map structure, I'd like to
> >  plug into that infrastructure, and create a new type memory segment
> >  for this storage (I envisage having more than one segment), but in the
> >  2.4.4 kernel (which I am forced to remain with for quite a while) it
> >  seems not to be used apart from set up at boot time.
> 
> Stop reinventing the wheel and take Matt & Pauline's bigphisarea.
>  http://www.polyware.nl/~middelink/patch/bigphysarea-2.4.4.tar.gz

Is bigphysarea needed in 2.4?   You have alloc_bootmem...

-- 
Jeff Garzik      | "I use Mandrake Linux for the same reason I turn
Building 1024    |  the light switch on and off 17 times before leaving
MandrakeSoft     |  the room.... If I don't my family will die."
                 |            -- slashdot.org comment

  reply	other threads:[~2001-07-25 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.996053899.5490.linux-kernel2news@redhat.com>
2001-07-25 22:00 ` Reserving large amounts of RAM for busmastering PCI card Pete Zaitcev
2001-07-25 22:05   ` Jeff Garzik [this message]
2001-07-26 12:29     ` Pete Zaitcev
2001-07-26 16:32       ` Jeff Garzik
2001-07-30 21:35         ` Pauline Middelink
2001-07-25  8:23 John P. Hartmann

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=3B5F428F.14DCAA44@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=LINUX-KERNEL@vger.kernel.org \
    --cc=john@vnet.ibm.com \
    --cc=zaitcev@redhat.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