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.

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

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

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

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

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Nov 20, 2014

Member

RFC 6056 describes alternate implementations we could apply to poolnum.

Member

ydahhrk commented Nov 20, 2014

RFC 6056 describes alternate implementations we could apply to poolnum.

@ydahhrk

This comment has been minimized.

Show comment
Hide comment
@ydahhrk

ydahhrk Mar 23, 2015

Member

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.

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 milestones: 3.3.3, 3.3.2 Mar 23, 2015

ydahhrk added a commit that referenced this issue Apr 28, 2015

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.

@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