Thread (7 messages) 7 messages, 3 authors, 2011-08-30

Re: [patch 2/2]slub: add a type for slab partial list position

From: Shaohua Li <hidden>
Date: 2011-08-30 01:50:04
Also in: lkml

On Mon, 2011-08-29 at 22:20 +0800, Christoph Lameter wrote:
On Mon, 29 Aug 2011, Alex,Shi wrote:
quoted
On Wed, 2011-08-24 at 08:57 +0800, Li, Shaohua wrote:
quoted
On Tue, 2011-08-23 at 23:25 +0800, Christoph Lameter wrote:
quoted
On Tue, 23 Aug 2011, Shaohua Li wrote:
quoted
Adding slab to partial list head/tail is sensentive to performance.
So adding a type to document it to avoid we get it wrong.
I think that if you want to make it more descriptive then using the stats
values (DEACTIVATE_TO_TAIL/HEAD) would avoid having to introduce an
additional enum and it would also avoid the if statement in the stat call.
ok, that's better.

Subject: slub: explicitly document position of inserting slab to partial list

Adding slab to partial list head/tail is sensitive to performance.
So explicitly uses DEACTIVATE_TO_TAIL/DEACTIVATE_TO_HEAD to document
it to avoid we get it wrong.
Frankly speaking, using DEACTIVATE_TO_TAIL/DEACTIVATE_TO_HEAD in
slab_alloc, slab_free make code hard to understand. Just adding some
comments will be more clear and understandable. like the following:
Do you think so?
Yes, I like that more.
fine, let me add it to the first patch


--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help