From: Jamie Lokier <jamie@shareable.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: open-scale-2.6.2-A0
Date: Wed, 11 Feb 2004 12:45:02 +0000 [thread overview]
Message-ID: <20040211124502.GG15127@mail.shareable.org> (raw)
In-Reply-To: <20040211122753.GA15129@elte.hu>
Ingo Molnar wrote:
> > Does this scalability improvement make any measured difference in any
> > conceivable application, or is it just making struct inode larger?
>
> i've not added any new lock, i'm merely reusing the existing ->i_lock.
> So there's no data or code bloat whatsoever.
Oh of course (duh!).
-- Jamie
next prev parent reply other threads:[~2004-02-11 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 11:58 open-scale-2.6.2-A0 Ingo Molnar
2004-02-11 12:20 ` open-scale-2.6.2-A0 Jamie Lokier
2004-02-11 12:27 ` open-scale-2.6.2-A0 Ingo Molnar
2004-02-11 12:45 ` Jamie Lokier [this message]
2004-02-11 20:39 ` open-scale-2.6.2-A0 Andrew Morton
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=20040211124502.GG15127@mail.shareable.org \
--to=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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