From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: 'Badari Pulavarty' <pbadari@us.ibm.com>,
Manfred Spraul <manfred@colorfullife.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm@kvack.org
Subject: RE: slab fragmentation ?
Date: Tue, 5 Oct 2004 15:11:38 -0700 [thread overview]
Message-ID: <200410052211.i95MBU630399@unix-os.sc.intel.com> (raw)
In-Reply-To: <1097010817.12861.164.camel@dyn318077bld.beaverton.ibm.com>
Badari Pulavarty wrote on Tuesday, October 05, 2004 2:14 PM
> > >>The fix would be simple: kmem_cache_alloc_node must walk through the
> > >>list of partial slabs and check if it finds a slab from the correct
> > >>node. If it does, then just use that slab instead of allocating a new
> > >>one.
>
> I don't see how to find out which slab came from which node. I don't
> think we save "nodeid" anywhere in the slab. Do we ?
If you have a pointer to the slab page, then you can traverse through
pgdat of each zone: page_zone(page)->zone_pgdat->node_id.
- Ken
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-05 22:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 23:36 slab fragmentation ? Badari Pulavarty
2004-09-30 3:41 ` Andrew Morton
2004-09-30 4:52 ` badari
2004-09-30 14:49 ` Martin J. Bligh
2004-09-30 14:48 ` Badari Pulavarty
2004-10-03 6:04 ` Manfred Spraul
2004-10-04 15:51 ` Badari Pulavarty
2004-10-04 16:08 ` Manfred Spraul
2004-10-04 17:37 ` Badari Pulavarty
2004-10-05 14:46 ` Badari Pulavarty
2004-10-05 17:58 ` Manfred Spraul
2004-10-05 18:27 ` Badari Pulavarty
2004-10-05 18:49 ` Manfred Spraul
2004-10-05 18:47 ` Badari Pulavarty
2004-10-05 21:13 ` Badari Pulavarty
2004-10-05 22:11 ` Chen, Kenneth W [this message]
2004-10-05 22:18 ` Chen, Kenneth W
2004-10-06 14:58 ` Badari Pulavarty
2004-10-09 14:28 ` Manfred Spraul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410052211.i95MBU630399@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=pbadari@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.