poolnum is using kmalloc to allocate some large arrays. #36

Closed
ydahhrk opened this Issue May 9, 2013 · 2 comments

Projects

None yet

1 participant

@ydahhrk
Member
ydahhrk commented May 9, 2013

Test case ID: N/A
Date: 2013/05/09
OS: N/A
Tester: AL
Error module: poolnum
Description: "If you need more than a few kilobytes (...) there are better ways than kmalloc to obtain memory" (http://lwn.net/images/pdf/LDD3/ch08.pdf).
We're allocating arrays of up to 128kb each.
Observations: -

@ydahhrk ydahhrk was assigned May 9, 2013
@ydahhrk
Member
ydahhrk commented Nov 20, 2014

RFC 6056 describes alternate implementations we could apply to poolnum.

@ydahhrk ydahhrk added this to the 3.3.1 milestone Jan 20, 2015
@ydahhrk ydahhrk modified the milestone: 3.3.1, 3.3.2 Mar 10, 2015
@ydahhrk
Member
ydahhrk commented Mar 23, 2015

I started this. It mangles pool4's API, which means it also requires some level of refactor on BIB and perhaps session. That makes this issue rather intrusive and risky.

Since 3.3.2 already has a lot of stuff that shouldn't be stalled, I'll move this to 3.3.3.

@ydahhrk ydahhrk modified the milestone: 3.3.3, 3.3.2 Mar 23, 2015
@ydahhrk ydahhrk added a commit that referenced this issue Apr 28, 2015
@ydahhrk ydahhrk Progress on #36.
Not sure why I haven't uploaded any of this in the week I've been working on it.
This is completely unstable, and meant as a backup checkpoint. Please don't think about running it.
2e24e3e
@ydahhrk ydahhrk closed this Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment