From: Hans Reiser <reiser@namesys.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Reiserfs mail-list <Reiserfs-List@namesys.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: short term task list for Reiser4
Date: Fri, 14 Jul 2006 00:05:48 -0700 [thread overview]
Message-ID: <44B7424C.3000108@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607131310570.29555@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
>On Thu, 13 Jul 2006, Hans Reiser wrote:
>
>
>
>>Christoph Lameter wrote:
>>
>>
>>
>>>Will there be any NUMA /SMP fixes? Reiserfs performance is severely
>>>impacted at higher processor counts by the mandatory centralized locking
>>>in both read and write paths in the filesystem.
>>>
>>>
>>Reiserfs or Reiser4?
>>
>>
>
>Either.
>
>
>
>
>
What big locks are you running into in V4? Please tell me more.
Hans
prev parent reply other threads:[~2006-07-14 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-11 22:04 short term task list for Reiser4 Hans Reiser
2006-07-11 22:29 ` Clay Barnes
2006-07-11 23:11 ` Hans Reiser
2006-07-11 23:55 ` Clay Barnes
2006-07-12 0:06 ` Hans Reiser
2006-07-13 19:17 ` Christoph Lameter
2006-07-13 19:53 ` Hans Reiser
2006-07-13 20:11 ` Christoph Lameter
2006-07-14 7:05 ` Hans Reiser [this message]
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=44B7424C.3000108@namesys.com \
--to=reiser@namesys.com \
--cc=Reiserfs-List@namesys.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@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