From: Peter Samuelson <peter@cadcamlab.org>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch-2.4.0-test12-pre5] optimized get_empty_filp()
Date: Tue, 5 Dec 2000 16:00:15 -0600 [thread overview]
Message-ID: <20001205160014.G6567@cadcamlab.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0012051754450.1493-100000@penguin.homenet>
In-Reply-To: <Pine.LNX.4.21.0012051754450.1493-100000@penguin.homenet>; from tigran@veritas.com on Tue, Dec 05, 2000 at 05:57:53PM +0000
[Tigran Aivazian]
> The only reason one could think of was to "hold the lock for as short
> time as possible" but a minute's thought reveals that such reason is
> invalid (i.e. one is more likely to waste time spinning on the lock
> than to save it by dropping/retaking it, given the relative duration
> of the instructions we execute there without the lock).
If there is no contention, you do not spin, no time wasted
If there *is* contention, you deserialize the routine just a little
bit, which is generally a Good Thing.
Whether a memset of 92 bytes (on 32-bit arch), plus an atomic_set(),
are worth deserializing, I do not know.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-05 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 17:57 Tigran Aivazian
2000-12-05 22:00 ` Peter Samuelson [this message]
2000-12-05 22:32 ` Tigran Aivazian
2000-12-05 22:50 ` Peter Samuelson
2000-12-06 7:03 ` Tigran Aivazian
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=20001205160014.G6567@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®