Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

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

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

ydahhrk opened this issue May 9, 2013 · 2 comments
Milestone
3.4.0

Comments

@ydahhrk
Copy link
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: -
@ghost ghost assigned ydahhrk May 9, 2013
@ydahhrk ydahhrk mentioned this issue May 9, 2013
Closed
@ydahhrk
Copy link
Member Author

ydahhrk commented Nov 20, 2014

RFC 6056 describes alternate implementations we could apply to poolnum.

@ydahhrk ydahhrk mentioned this issue Nov 21, 2014
Closed
@ydahhrk ydahhrk added this to the 3.3.1 milestone Jan 20, 2015
@ydahhrk ydahhrk modified the milestones: 3.3.1, 3.3.2 Mar 10, 2015
@ydahhrk ydahhrk mentioned this issue Mar 23, 2015
Closed
@ydahhrk
Copy link
Member Author

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 milestones: 3.3.3, 3.3.2 Mar 23, 2015
ydahhrk added a commit that referenced this issue Apr 28, 2015
@ydahhrk
Progress on #36.
2e24e3e 
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.
@ydahhrk ydahhrk closed this as completed Nov 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
3.4.0
Development

No branches or pull requests
1 participant
@ydahhrk