From: Christoph Hellwig <hch@infradead.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: [PATCH] make lock/release_sock fast calls
Date: Thu, 1 Apr 2004 05:45:21 +0100 [thread overview]
Message-ID: <20040401054521.A16112@infradead.org> (raw)
In-Reply-To: <20040331112407.66309027@dell_ss3.pdx.osdl.net>; from shemminger@osdl.org on Wed, Mar 31, 2004 at 11:24:07AM -0800
On Wed, Mar 31, 2004 at 11:24:07AM -0800, Stephen Hemminger wrote:
> lock_sock and release_sock are no longer inline, but they are called in
> the critical path of many operations, so it makes sense to use register based
> fastcall.
Not sure I agree. If you care for performance you compile with
CONFIG_REGPARAM set, no?
next prev parent reply other threads:[~2004-04-01 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 19:24 [PATCH] make lock/release_sock fast calls Stephen Hemminger
2004-04-01 4:45 ` Christoph Hellwig [this message]
2004-04-01 7:07 ` David S. Miller
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=20040401054521.A16112@infradead.org \
--to=hch@infradead.org \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--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;
as well as URLs for NNTP newsgroup(s).