From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: john@vnet.ibm.com, LINUX-KERNEL@vger.kernel.org
Subject: Re: Reserving large amounts of RAM for busmastering PCI card.
Date: Thu, 26 Jul 2001 08:29:25 -0400 [thread overview]
Message-ID: <20010726082925.B2322@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.996053899.5490.linux-kernel2news@redhat.com> <200107252200.f6PM0IJ01020@devserv.devel.redhat.com> <3B5F428F.14DCAA44@mandrakesoft.com>
In-Reply-To: <3B5F428F.14DCAA44@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Wed, Jul 25, 2001 at 06:05:03PM -0400
> > > 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...
I thought bigphisarea allowed to unload and reload modules,
at least I used it that way with C-cube MPEG board. Makes
for faster tests.
-- Pete
next prev parent reply other threads:[~2001-07-26 12:29 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
2001-07-26 12:29 ` Pete Zaitcev [this message]
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=20010726082925.B2322@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=LINUX-KERNEL@vger.kernel.org \
--cc=jgarzik@mandrakesoft.com \
--cc=john@vnet.ibm.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