From: Hugh Dickins <hugh@veritas.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Ulrich Drepper <drepper@redhat.com>,
Andrew Morton <akpm@osdl.org>,
Stephen Hemminger <shemminger@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: today's futex changes
Date: Sat, 6 Sep 2003 19:21:33 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0309061916530.1177-100000@localhost.localdomain> (raw)
In-Reply-To: <20030906174615.GA10987@mail.jlokier.co.uk>
On Sat, 6 Sep 2003, Jamie Lokier wrote:
> > And save a few bytes and improve debuggability
> > by uninlining the top-level futex_wake, futex_requeue, futex_wait.
>
> Fair point about about debuggability, but does it really save bytes to
> uninline these called-once functions?
It saved about 50 with whatever 2.96 I'm using on this machine, but I
didn't try other gccs; it's probably added about that back in kallsyms...
Hugh
next prev parent reply other threads:[~2003-09-06 18:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 20:24 today's futex changes Ulrich Drepper
2003-09-05 22:24 ` Stephen Hemminger
2003-09-06 16:28 ` [PATCH] " Hugh Dickins
2003-09-06 17:32 ` Ulrich Drepper
2003-09-06 17:44 ` Jamie Lokier
2003-09-06 17:46 ` Jamie Lokier
2003-09-06 18:21 ` Hugh Dickins [this message]
2003-09-08 6:45 ` Rusty Russell
2003-09-08 17:33 ` Hugh Dickins
2003-09-08 17:51 ` Hugh Dickins
2003-09-09 1:37 ` Rusty Russell
2003-09-08 17:51 ` Jamie Lokier
2003-09-08 18:26 ` Jamie Lokier
2003-09-09 3:58 ` Rusty Russell
2003-09-10 11:39 ` Jamie Lokier
2003-09-10 22:00 ` Rusty Russell
2003-09-11 16:29 ` Jamie Lokier
2003-09-08 19:02 ` Andrew Morton
2003-09-08 20:07 ` Jamie Lokier
2003-09-08 19:59 ` Andrew Morton
2003-09-08 20:11 ` Linus Torvalds
2003-09-09 4:12 ` Rusty Russell
2003-09-08 17:04 ` Stephen Hemminger
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=Pine.LNX.4.44.0309061916530.1177-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@osdl.org \
--cc=torvalds@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).