From: Christoph Lameter <cl@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH next 1/3] slub defrag: unpin writeback pages
Date: Tue, 07 Oct 2008 08:24:09 -0500 [thread overview]
Message-ID: <48EB62F9.9040409@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0810050319001.22004@blonde.site>
Hugh Dickins wrote:
> A repetitive swapping load on powerpc G5 went progressively slower after
> nine hours: Inactive(file) was rising, as if inactive file pages pinned.
> Yes, slub defrag's kick_buffers() was forgetting to put_page() whenever
> it met a page already under writeback.
Thanks for finding that.
> That PageWriteback test should be made while PageLocked in trigger_write(),
> just as it is in try_to_free_buffers() - if there are complex reasons why
> that's not actually necessary, I'd rather not have to think through them.
> A preliminary check before taking the lock? No, it's not that important.
The writeback check in kick_buffers() is a performance optimization. If the
page is under writeback then there is no point in trying to kick out the page.
That will only succeed after writeback is complete.
If a page is under writeback then try_to_free_buffers() will fail immediately.
So no need to check under pagelock.
> And trigger_write() must remember to unlock_page() in each of the cases
> where it doesn't reach the writepage().
Ack.
> --- 2.6.27-rc7-mmotm/fs/buffer.c 2008-09-26 13:18:50.000000000 +0100
> +++ linux/fs/buffer.c 2008-10-03 19:43:44.000000000 +0100
> @@ -3354,13 +3354,16 @@ static void trigger_write(struct page *p
> .for_reclaim = 0
> };
>
> + if (PageWriteback(page))
> + goto unlock;
> +
Is that necessary? Wont writepage do the appropriate thing?
> /*
> @@ -3420,7 +3423,7 @@ static void kick_buffers(struct kmem_cac
> for (i = 0; i < nr; i++) {
> page = v[i];
>
> - if (!page || PageWriteback(page))
> + if (!page)
> continue;
Thats just an optimization. No need to lock a page if its under writeback
which would make try_to_free_buffers() fail.
--
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>
next prev parent reply other threads:[~2008-10-07 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 2:25 Hugh Dickins
2008-10-05 2:27 ` [PATCH next 2/3] slub defrag: dma_kmalloc_cache add_tail Hugh Dickins
2008-10-06 7:46 ` Pekka Enberg
2008-10-07 13:25 ` Christoph Lameter
2008-10-05 2:28 ` [PATCH next 3/3] slub defrag: slabinfo help trivia Hugh Dickins
2008-10-06 7:40 ` Pekka Enberg
2008-10-06 7:53 ` [PATCH next 1/3] slub defrag: unpin writeback pages Pekka Enberg
2008-10-07 13:24 ` Christoph Lameter [this message]
2008-10-07 15:34 ` Hugh Dickins
2008-10-07 15:41 ` Christoph Lameter
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=48EB62F9.9040409@linux-foundation.org \
--to=cl@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--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