Bug 765206 (GLUSTER-3474)

Summary: iobuf arenas should have fixed number of pages instead of fixed arena size
Product: [Community] GlusterFS Reporter: Amar Tumballi <amarts>
Component: coreAssignee: Amar Tumballi <amarts>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Amar Tumballi 2011-08-24 06:32:04 UTC
with the current variable sized io-buf, we saw that the arena size for all the page sizes are constant (which is 8MB, given during the init time).

instead it should be fixed number of pages. So, the 'iobuf_arean_init()' should take 'page-size' and 'page-count' as argument.

Comment 1 Amar Tumballi 2011-08-28 04:30:25 UTC
Had chat with this with Avati. We can't hardcode page-count of all the arena to a single value. (as in, for a 8MB buffer (may be required if we allow quick-read cache-size option to 8MB, and if we have hardcoded value of 64, it will be like 512MB for a single arena).

We should have something like a configurable page-count for different sizes of the page. May be like 2k buffers can have 256 pages, where as 256k buffers can be just 16. etc etc.. Will come up with more proper design before solving this.

Comment 2 Amar Tumballi 2011-09-27 05:50:04 UTC
Planing to keep 3.4.x branch as "internal enhancements" release without any features. So moving these bugs to 3.4.0 target milestone.

Comment 3 Anand Avati 2011-12-07 10:01:56 UTC
CHANGE: http://review.gluster.com/543 (* so overall memory usage will be in limit.) merged in master by Anand Avati (avati)