Skip to contentSkip to conversation

Reserving large amounts of RAM for busmastering PCI card.

DISCUSSION Pete Zaitcev 3 participants 5 messages Jul 25, 2001 – Jul 30, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 5 lines

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

-- Pete

#2 lore raw
In reply to a message not in the archive
Quoted 9 lines · Pete Zaitcev
Quoted 6 lines

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...

Signature · 4 lines
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
#3 lore raw
In reply to a message not in the archive
Quoted 10 lines
Quoted 8 lines
Quoted 5 lines

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

#4 lore raw
In reply to a message not in the archive
Quoted 7 lines · Pete Zaitcev
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

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...

Signature · 4 lines
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
#5 lore raw
In reply to a message not in the archive
Quoted 17 lines · Jeff Garzik
Quoted 7 lines · Pete Zaitcev
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines

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.

Quoted 8 lines
Quoted 4 lines
Quoted 2 lines

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.

Quoted 5 lines

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

Signature · 2 lines
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