public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pauline Middelink <middelink@polyware.nl>
To: LINUX-KERNEL@vger.kernel.org
Subject: Re: Reserving large amounts of RAM for busmastering PCI card.
Date: Mon, 30 Jul 2001 23:35:58 +0200	[thread overview]
Message-ID: <20010730233558.A19009@polyware.nl> (raw)
In-Reply-To: <mailman.996053899.5490.linux-kernel2news@redhat.com> <200107252200.f6PM0IJ01020@devserv.devel.redhat.com> <3B5F428F.14DCAA44@mandrakesoft.com> <20010726082925.B2322@devserv.devel.redhat.com> <3B604612.F5FCC8E7@mandrakesoft.com>
In-Reply-To: <3B604612.F5FCC8E7@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Thu, Jul 26, 2001 at 12:32:18PM -0400

On Thu, 26 Jul 2001 around 12:32:18 -0400, Jeff Garzik wrote:
> 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...
> > 
> > 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.
> 
> AFAICS this is only useful to developers, not end users, yes?
> 
> Memory will get fragmented if done at some time other than boot, so
> module loads will randomly fail based on conditions unrelated to the
> module at hand.  It's not a reliable operation, as a module...

No, bigphysarea takes it memory from bootmem not from kmalloc, and
gives it out to requesters of contingious memory.
When used with modules (like my zoran driver, it alloc at driver
open time and frees the memory at driver close time, giving the
user a second chance at nicely grabbed pictures :) )

    Met vriendelijke groet,
        Pauline Middelink
-- 
GPG Key fingerprint = 2D5B 87A7 DDA6 0378 5DEA  BD3B 9A50 B416 E2D0 C3C2
For more details look at my website http://www.polyware.nl/~middelink

  reply	other threads:[~2001-07-30 21:36 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
2001-07-26 16:32       ` Jeff Garzik
2001-07-30 21:35         ` Pauline Middelink [this message]
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=20010730233558.A19009@polyware.nl \
    --to=middelink@polyware.nl \
    --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