linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alok kataria <alokkataria1@gmail.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
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 01:20:14 +0530	[thread overview]
Message-ID: <35f686220509151250e598fda@mail.gmail.com> (raw)
In-Reply-To: <4317F50B.6080005@yahoo.com.au>

[-- Attachment #1: Type: text/plain, Size: 1672 bytes --]

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.

Thanks & Regards,
Alok


On 9/2/05, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Nick Piggin wrote:
> 
> > I think this is getting pretty stable. No guarantees of course,
> > but it would be great if anyone gave it a test.
> >
> 
> Or review, I might add. While I understand such a review is
> still quite difficult, this code really is far less complex
> than the previous lockless pagecache patches.
> 
> (Ignore 1/7 though, which is a rollup - a broken out patchset
> can be provided on request)
> 
> Nick
> 
> --
> SUSE Labs, Novell Inc.
> 
> Send instant messages to your online friends http://au.messenger.yahoo.com
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
A computer scientist is someone who, when told to "Go to Hell," sees
the "go to," rather than the destination, as harmful.

Alok Kataria

[-- Attachment #2: lockless-pagecache.tjz --]
[-- Type: application/octet-stream, Size: 53665 bytes --]

  reply	other threads:[~2005-09-15 19:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 15:23                 ` Nick Piggin
2005-09-09  5:36           ` [PATCH 2.6.13] lockless pagecache 5/7 Christoph Lameter
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 20:41       ` Andi Kleen
2005-09-02 21:12         ` David S. Miller, Andi Kleen
2005-09-02 21:43           ` Nick Piggin
2005-09-02 21:22         ` Nick Piggin
2005-09-02 21:31           ` David S. Miller, Nick Piggin
2005-09-02 21:47             ` Nick Piggin
2005-09-02 21:57               ` David S. Miller, Nick Piggin
2005-09-02 23:57           ` Alan Cox
2005-09-03  1:40             ` Nick Piggin
2005-09-03 17:31               ` Alan Cox
2005-09-04  1:01                 ` Nick Piggin
2005-09-04  8:20                   ` Alan Cox
2005-09-06  1:03                     ` Nick Piggin
2005-09-02 18:26     ` Christoph Lameter
2005-09-02 21:26       ` Nick Piggin
2005-09-03  1:33         ` Christoph Lameter
2005-09-02  6:45 ` New lockless pagecache Nick Piggin
2005-09-15 19:50   ` Alok kataria [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=35f686220509151250e598fda@mail.gmail.com \
    --to=alokkataria1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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