From: Andrea Arcangeli <andrea@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@digeo.com>,
davem@redhat.com, shemminger@osdl.org, rmk@arm.linux.org.uk,
ak@muc.de, davidm@napali.hpl.hp.com, anton@samba.org,
linux-mm@kvack.org, rth@twiddle.net
Subject: Re: Linus rollup
Date: Thu, 30 Jan 2003 03:03:59 +0100 [thread overview]
Message-ID: <20030130020359.GV1237@dualathlon.random> (raw)
In-Reply-To: <3E3884DA.9060600@pobox.com>
On Wed, Jan 29, 2003 at 08:50:18PM -0500, Jeff Garzik wrote:
> Andrew Morton wrote:
> >#ifndef __LINUX_FRLOCK_H
> >#define __LINUX_FRLOCK_H
> >
> >/*
> > * Fast read-write spinlocks.
>
>
> Can we please pick a unique name whose meaning will not change over
> time? Even "andre[wa]_rw_lock" would be better, because its meaning is
I was the first to use it in practice in linux for gettimeofday in the
x86-64 port, but it should be called "keith_owens_lock" if really you
like to use the inventor name. I was trying to find this kind of
readonly read-side lock while designing the vgettimeofday the first time
it was discussed ever on l-k a few years back (way before it seen the
light of the day), and during such discussion Keith shown me the light,
so it wouldn't be fair to take credit for it ;). If you search l-k
probably in y2k or near you should find that email from Keith in answer
to me.
> not tied to performance at this specific point in time, on today's ia32
> flavor-of-the-month.
>
> If we discover even-yet-faster read-write spinlocks tomorrow, this name
> is going to become a joke :)
it would become historical, like so many other things. Actually when
they say frlock I don't even think at fast read lock, I think at frlock
as a specific new name, so personally I'm fine either ways. I don't
dislike it, it's not worse than the big reader lock name that should be
replaced by RCU at large btw.
Andrea
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2003-01-30 2:03 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 6:07 Andrew Morton
2003-01-29 6:53 ` David Mosberger
2003-01-29 7:25 ` David S. Miller
2003-01-29 9:33 ` Andrew Morton
2003-01-29 9:35 ` David S. Miller
2003-01-29 9:54 ` Anton Blanchard
2003-01-29 9:59 ` Russell King
2003-01-29 9:51 ` David S. Miller
2003-01-29 10:26 ` Andrew Morton
2003-01-29 22:35 ` Stephen Hemminger
2003-01-29 23:12 ` Andrew Morton
2003-01-30 0:30 ` David S. Miller
2003-01-30 1:27 ` Andrew Morton
2003-01-30 1:24 ` Andi Kleen
2003-01-30 2:01 ` Andrew Morton
2003-01-30 1:35 ` Andrea Arcangeli
2003-01-30 2:00 ` Andrew Morton
2003-01-30 1:50 ` Jeff Garzik
2003-01-30 2:03 ` Andrea Arcangeli [this message]
2003-01-30 17:09 ` Stephen Hemminger
2003-01-30 17:15 ` Randy.Dunlap
2003-01-30 17:25 ` Andi Kleen
2003-01-30 17:23 ` Randy.Dunlap
2003-01-30 1:52 ` Richard Henderson
2003-01-30 2:06 ` Andrea Arcangeli
2003-01-30 1:54 ` Andrea Arcangeli
2003-01-30 2:19 ` Andrew Morton
2003-01-30 17:37 ` Stephen Hemminger
2003-01-30 17:50 ` Andrea Arcangeli
2003-01-30 2:00 ` Richard Henderson
2003-01-30 0:46 ` Andrea Arcangeli
2003-01-30 0:43 ` Andrea Arcangeli
2003-01-29 10:16 ` Andrew Morton
2003-01-29 17:04 ` David Mosberger
2003-01-29 17:25 ` Russell King
2003-01-29 19:05 ` David Mosberger
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=20030130020359.GV1237@dualathlon.random \
--to=andrea@suse.de \
--cc=ak@muc.de \
--cc=akpm@digeo.com \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=davidm@napali.hpl.hp.com \
--cc=jgarzik@pobox.com \
--cc=linux-mm@kvack.org \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
--cc=shemminger@osdl.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