linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>, linux-mm@kvack.org
Subject: [patch] slab: fix regression in touched logic
Date: Wed, 27 Jan 2010 22:27:40 +1100	[thread overview]
Message-ID: <20100127112740.GA14790@laptop> (raw)

Hi,

This hasn't actually shown up in any real workloads, but if my following
logic is correct then it should be a good fix. Comments?

Thanks,
Nick
--

When factoring common code into transfer_objects, the 'touched' logic
got a bit broken. When refilling from the shared array (taking objects
from the shared array), we are making use of the shared array so it
should be marked as touched.

Subsequently pulling an element from the cpu array and allocating it
should also touch the cpu array, but that is taken care of after the
alloc_done label. (So yes, the cpu array was getting touched = 1
twice).

So revert this logic to how it worked in earlier kernels.

This also affects the behaviour in __drain_alien_cache, which would
previously 'touch' the shared array and now does not. I think it is
more logical not to touch there, because we are pushing objects into
the shared array rather than pulling them off. So there is no good
reason to postpone reaping them -- if the shared array is getting
utilized, then it will get 'touched' in the alloc path (where this
patch now restores the touch).

Signed-off-by: Nick Piggin <npiggin@suse.de>
---
Index: linux-2.6/mm/slab.c
===================================================================
--- linux-2.6.orig/mm/slab.c
+++ linux-2.6/mm/slab.c
@@ -935,7 +935,6 @@ static int transfer_objects(struct array
 
 	from->avail -= nr;
 	to->avail += nr;
-	to->touched = 1;
 	return nr;
 }
 
@@ -2963,8 +2962,10 @@ retry:
 	spin_lock(&l3->list_lock);
 
 	/* See if we can refill from the shared array */
-	if (l3->shared && transfer_objects(ac, l3->shared, batchcount))
+	if (l3->shared && transfer_objects(ac, l3->shared, batchcount)) {
+		l3->shared->touched = 1;
 		goto alloc_done;
+	}
 
 	while (batchcount > 0) {
 		struct list_head *entry;

--
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:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2010-01-27 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 11:27 Nick Piggin [this message]
2010-01-27 15:13 ` [patch] slab: fix regression in touched logic Pekka Enberg
2010-01-27 15:29   ` Nick Piggin
2010-01-27 17:49 ` Christoph Lameter
2010-01-30 13:07   ` Pekka Enberg

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=20100127112740.GA14790@laptop \
    --to=npiggin@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).