From: Andrew Morton <akpm@osdl.org>
To: Benjamin LaHaise <bcrl@linux.intel.com>
Cc: linux-mm@kvack.org, netdev@vger.kernel.org
Subject: Re: [PATCH] avoid atomic op on page free
Date: Mon, 6 Mar 2006 16:50:39 -0800 [thread overview]
Message-ID: <20060306165039.1c3b66d8.akpm@osdl.org> (raw)
In-Reply-To: <20060307001015.GG32565@linux.intel.com>
Benjamin LaHaise <bcrl@linux.intel.com> wrote:
>
> Hello Andrew et al,
>
> The patch below adds a fast path that avoids the atomic dec and test
> operation and spinlock acquire/release on page free. This is especially
> important to the network stack which uses put_page() to free user
> buffers. Removing these atomic ops helps improve netperf on the P4
> from ~8126Mbit/s to ~8199Mbit/s (although that number fluctuates quite a
> bit with some runs getting 8243Mbit/s). There are probably better
> workloads to see an improvement from this on, but removing 3 atomics and
> an irq save/restore is good.
>
Am a bit surprised at those numbers.
> diff --git a/mm/swap.c b/mm/swap.c
> index cce3dda..d6934cf 100644
> --- a/mm/swap.c
> +++ b/mm/swap.c
> @@ -49,7 +49,10 @@ void put_page(struct page *page)
> {
> if (unlikely(PageCompound(page)))
> put_compound_page(page);
> - else if (put_page_testzero(page))
> + else if (page_count(page) == 1 && !PageLRU(page)) {
> + set_page_count(page, 0);
> + free_hot_page(page);
> + } else if (put_page_testzero(page))
> __page_cache_release(page);
Because userspace has to do peculiar things to get its pages taken off the
LRU. What exactly was that application doing?
The patch adds slight overhead to the common case while providing
improvement to what I suspect is a very uncommon case?
--
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:[~2006-03-07 0:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 0:10 Benjamin LaHaise
2006-03-07 0:50 ` Andrew Morton [this message]
2006-03-07 1:11 ` Benjamin LaHaise
2006-03-07 1:39 ` Andrew Morton
2006-03-07 1:52 ` Benjamin LaHaise
2006-03-07 6:30 ` Andi Kleen
2006-03-07 2:04 ` Nick Piggin
2006-03-07 2:10 ` Benjamin LaHaise
2006-03-07 4:08 ` Nick Piggin
2006-03-07 2:30 ` Chen, Kenneth W
2006-03-07 4:13 ` Nick Piggin
2006-03-07 1:21 ` Rick Jones
2006-03-07 1:53 ` Nick Piggin
2006-03-07 1:58 ` Benjamin LaHaise
2006-03-07 2:14 ` Nick Piggin
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=20060306165039.1c3b66d8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bcrl@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
/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