From: Nick Piggin <nickpiggin@yahoo.com.au>
To: alokkataria1@gmail.com
Cc: Linux Memory Management <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: New lockless pagecache
Date: Fri, 16 Sep 2005 13:12:16 +1000 [thread overview]
Message-ID: <432A3810.9070600@yahoo.com.au> (raw)
In-Reply-To: <35f686220509151250e598fda@mail.gmail.com>
Alok kataria wrote:
> Hi Nick,
>
> I have collected performance numbers for the lock less page cache
> patch on the AIM - IO test.
> The performance numbers are collected for 1-100 tasks 1-50 tasks and
> 90-100 tasks both for with and without your patch. This was done on
> 2.6.13 kernel.
> There's definite improvement when the tasks are small i.e ~50-70. But
> when the tasks go beyond 80, we see a large performance dip.
> I again profiled the 90-100 runs with spinlock's inlined, but couldn't
> understand the reason behind the performance difference.
>
> Please find attached the performance numbers as well as the oprofile logs.
>
Hi Alok,
Thanks very much for doing these numbers. Performance is improved
significantly at smaller numbers of tasks, as you say.
Unfortunately I can't pinpoint the reason why performance drops at
larger numbers. I could assume that the last remaining place that
used read_lock_irq for the tree_lock (wait_on_page_writeback_range)
got hurt when switching to spinlocks, but that would seem vary
unlikely.
I'll have to look into it further.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: alokkataria1@gmail.com
Cc: Linux Memory Management <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: New lockless pagecache
Date: Fri, 16 Sep 2005 13:12:16 +1000 [thread overview]
Message-ID: <432A3810.9070600@yahoo.com.au> (raw)
In-Reply-To: <35f686220509151250e598fda@mail.gmail.com>
Alok kataria wrote:
> Hi Nick,
>
> I have collected performance numbers for the lock less page cache
> patch on the AIM - IO test.
> The performance numbers are collected for 1-100 tasks 1-50 tasks and
> 90-100 tasks both for with and without your patch. This was done on
> 2.6.13 kernel.
> There's definite improvement when the tasks are small i.e ~50-70. But
> when the tasks go beyond 80, we see a large performance dip.
> I again profiled the 90-100 runs with spinlock's inlined, but couldn't
> understand the reason behind the performance difference.
>
> Please find attached the performance numbers as well as the oprofile logs.
>
Hi Alok,
Thanks very much for doing these numbers. Performance is improved
significantly at smaller numbers of tasks, as you say.
Unfortunately I can't pinpoint the reason why performance drops at
larger numbers. I could assume that the last remaining place that
used read_lock_irq for the tree_lock (wait_on_page_writeback_range)
got hurt when switching to spinlocks, but that would seem vary
unlikely.
I'll have to look into it further.
Thanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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:[~2005-09-16 3:12 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 6:25 New lockless pagecache Nick Piggin
2005-09-02 6:25 ` Nick Piggin
2005-09-02 6:28 ` [PATCH 2.6.13] lockless pagecache 1/7 Nick Piggin
2005-09-02 6:29 ` [PATCH 2.6.13] lockless pagecache 2/7 Nick Piggin
2005-09-02 6:30 ` [PATCH 2.6.13] lockless pagecache 3/7 Nick Piggin
2005-09-02 6:30 ` [PATCH 2.6.13] lockless pagecache 4/7 Nick Piggin
2005-09-02 6:31 ` [PATCH 2.6.13] lockless pagecache 5/7 Nick Piggin
2005-09-02 6:32 ` [PATCH 2.6.13] lockless pagecache 6/7 Nick Piggin
2005-09-02 6:32 ` [PATCH 2.6.13] lockless pagecache 7/7 Nick Piggin
2005-09-09 13:00 ` Christoph Lameter
2005-09-09 13:00 ` Christoph Lameter
2005-09-09 15:23 ` Nick Piggin
2005-09-09 15:23 ` Nick Piggin
2005-09-09 5:36 ` [PATCH 2.6.13] lockless pagecache 5/7 Christoph Lameter
2005-09-09 5:36 ` Christoph Lameter
2005-09-09 6:22 ` Nick Piggin
2005-09-09 6:22 ` Nick Piggin
2005-09-02 13:08 ` [PATCH 2.6.13] lockless pagecache 2/7 Alan Cox
2005-09-02 13:08 ` Alan Cox
2005-09-02 20:41 ` Andi Kleen
2005-09-02 20:41 ` Andi Kleen
2005-09-02 21:12 ` David S. Miller
2005-09-02 21:12 ` David S. Miller, Andi Kleen
2005-09-02 21:43 ` Nick Piggin
2005-09-02 21:43 ` Nick Piggin
2005-09-02 21:22 ` Nick Piggin
2005-09-02 21:22 ` Nick Piggin
2005-09-02 21:31 ` David S. Miller
2005-09-02 21:31 ` David S. Miller, Nick Piggin
2005-09-02 21:47 ` Nick Piggin
2005-09-02 21:47 ` Nick Piggin
2005-09-02 21:57 ` David S. Miller
2005-09-02 21:57 ` David S. Miller, Nick Piggin
2005-09-02 23:57 ` Alan Cox
2005-09-02 23:57 ` Alan Cox
2005-09-03 1:40 ` Nick Piggin
2005-09-03 1:40 ` Nick Piggin
2005-09-03 17:31 ` Alan Cox
2005-09-03 17:31 ` Alan Cox
2005-09-04 1:01 ` Nick Piggin
2005-09-04 1:01 ` Nick Piggin
2005-09-04 8:20 ` Alan Cox
2005-09-04 8:20 ` Alan Cox
2005-09-06 1:03 ` Nick Piggin
2005-09-06 1:03 ` Nick Piggin
2005-09-02 18:26 ` Christoph Lameter
2005-09-02 18:26 ` Christoph Lameter
2005-09-02 21:26 ` Nick Piggin
2005-09-02 21:26 ` Nick Piggin
2005-09-03 1:33 ` Christoph Lameter
2005-09-03 1:33 ` Christoph Lameter
2005-09-02 6:45 ` New lockless pagecache Nick Piggin
2005-09-02 6:45 ` Nick Piggin
2005-09-15 19:50 ` Alok kataria
2005-09-16 3:12 ` Nick Piggin [this message]
2005-09-16 3:12 ` 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=432A3810.9070600@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=alokkataria1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.