From: maht <maht-9fans@maht0x0r.net>
To: 9fans@9fans.net
Subject: Re: [9fans] quote o' the day
Date: Thu, 25 Mar 2010 15:04:26 +0000 [thread overview]
Message-ID: <4BAB7B7A.60904@maht0x0r.net> (raw)
In-Reply-To: <09878a44d12791405e8b8b2bebb140f4@ladd.quanstro.net>
On 25/03/2010 14:08, erik quanstrom wrote:
> http://lwn.net/Articles/378219/
> "[...] anything which combines tricky locking
> and 30-line preprocessor macros is going to raise eyebrows.
> But the core concept here is simple: [...]
>
> oh, really?
>
> - erik
>
>
Trying to acquire one lock per CPU will work just dandy.
> One such case - the target for this new lock - is vfsmount_lock,
which is required (for read access) in pathname lookup operations.
Lookups are frequent events, and are clearly performance-critical. On
the other hand, write access is only needed when filesystems are being
mounted or unmounted - a much rarer occurrence. So a brlock is a good
fit here, and one small piece (out of many) of the VFS scalability
puzzle has been put into place.
bye bye private Linux namespaces, it wasn't even nice knowing you
next prev parent reply other threads:[~2010-03-25 15:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 14:08 erik quanstrom
2010-03-25 15:04 ` maht [this message]
2010-03-25 16:56 ` ron minnich
2010-03-25 17:11 ` Corey Thomasson
2010-03-25 17:15 ` maht
2010-03-25 17:26 ` Corey Thomasson
2010-03-25 17:33 ` Robert Raschke
2010-03-25 17:42 ` David Leimbach
2010-03-25 17:29 ` erik quanstrom
2010-03-25 17:31 ` blstuart
2010-03-25 16:44 ` Patrick Kelly
2010-03-25 18:31 ` blstuart
2010-03-25 18:33 ` andrey mirtchovski
2010-03-25 18:37 ` erik quanstrom
2010-03-25 18:51 ` blstuart
2010-03-25 21:17 ` Francisco J Ballesteros
2010-03-25 20:26 ` Patrick Kelly
2010-03-25 21:58 ` Tim Newsham
2010-03-25 21:21 ` Patrick Kelly
2010-03-25 22:37 ` Justin Jackson
2010-03-25 22:53 ` erik quanstrom
2010-03-25 22:57 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-03-26 0:03 ` Anthony Sorace
2010-03-26 2:16 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-03-26 6:43 ` Tim Newsham
2010-03-26 13:54 ` andrey mirtchovski
2010-03-28 23:22 ` Jack Johnson
2010-03-26 0:36 ` Corey Thomasson
2010-03-26 9:19 ` hugo rivera
2010-03-28 23:05 ` Eris Discordia
[not found] ` <989B4954D6C952C13793229D@192.168.1.2>
2010-03-28 23:31 ` hiro
2010-03-28 23:41 ` Connor Lane Smith
2010-03-28 23:51 ` hiro
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=4BAB7B7A.60904@maht0x0r.net \
--to=maht-9fans@maht0x0r.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).