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,
-- 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 21:00:46 EST