public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Bron Gondwana <brong@fastmail.fm>
Cc: Andi Kleen <andi@firstfloor.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Jeff Mahoney <jeffm@suse.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	ReiserFS Development List <reiserfs-devel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] reiserfs: kill-the-BKL
Date: Fri, 10 Apr 2009 15:07:35 +0200	[thread overview]
Message-ID: <20090410130735.GC31307@elte.hu> (raw)
In-Reply-To: <20090410003947.GA21681@brong.net>


* Bron Gondwana <brong@fastmail.fm> wrote:

> > For example, if you have /home and / on separate reiser3 
> > filesystems, you could see as much as a 200% jump in performance 
> > straight away on certain workloads, on a dual-core box.
> > 
> > That big BKL overhead is a real reiser3 scalability problem - 
> > especially on reiser3 using servers which are likely to have 
> > several filesystems on the same box.
> 
> Yes - I'm certainly interested in that.
> 
> That said, we have a box with 83 reiserfs partitions on it, and 
> which is constrained by IO (main servers really don't need much 
> CPU).  Performance is pretty good even now.
> 
> So - I'm interested in this patch series, but not at the expense 
> of making reiserfs any less stable.  Our customers, funnily 
> enough, like it when our service is stable!

Definitely so :-)

	Ingo

  reply	other threads:[~2009-04-10 13:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07  2:19 [PATCH] reiserfs: kill-the-BKL Frederic Weisbecker
2009-04-07 11:24 ` Frederic Weisbecker
2009-04-07 13:40 ` Ingo Molnar
2009-04-07 21:34 ` Alexander Beregalov
2009-04-07 21:57   ` Frederic Weisbecker
2009-04-07 22:19     ` Alexander Beregalov
2009-04-08  0:42       ` Frederic Weisbecker
2009-04-09 15:15 ` Andi Kleen
2009-04-09 15:35   ` Linus Torvalds
2009-04-09 18:40     ` Ingo Molnar
2009-04-09 19:36       ` Andi Kleen
2009-04-09 20:05         ` Frederic Weisbecker
2009-04-09 21:17         ` Ingo Molnar
2009-04-10  0:39           ` Bron Gondwana
2009-04-10 13:07             ` Ingo Molnar [this message]
2009-04-09 21:07   ` Ingo Molnar

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=20090410130735.GC31307@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=brong@fastmail.fm \
    --cc=fweisbec@gmail.com \
    --cc=jeffm@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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