From: Andi Kleen <ak@suse.de>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, linux-arch@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] fixing sendfile on 64bit architectures
Date: Wed, 19 May 2004 21:01:56 +0200 [thread overview]
Message-ID: <20040519210156.2a983a7c.ak@suse.de> (raw)
In-Reply-To: <16555.42184.694738.917744@napali.hpl.hp.com>
On Wed, 19 May 2004 11:17:44 -0700
David Mosberger <davidm@napali.hpl.hp.com> wrote:
>
> The patch looks fine to me. My only minor quibble is that it would be
> nice if sys_sendfile() wasn't defined at all when it isn't needed and,
> in that case, do_sendfile() should be inlined (unit-at-a-time
> compilation will take care of the inlining if sys_sendfile() isn't
> defined when not needed, so that part doesn't require extra code).
And I thought IA64 didn't care about code size... ;-)
>
> I don't like adding yet another "#ifdef __ia64 && ..." though. It
> would be nice if there was a cleaner way to get rid of unwanted
> syscall-stubs in generic code. How would people feel about replacing
> the current #ifdef mess with "#ifdef SYS_NEED_foo" instead? By my
> count, that would get rid of about a dozen of those ugly #ifdefs. For
> example, in fs/stat.c we could have:
>
> #ifdef SYS_NEED_OLD_STAT
>
> instead of:
>
> #if !defined(__alpha__) && !defined(__sparc__) && !defined(__ia64__) \
> && !defined(CONFIG_ARCH_S390) && !defined(__hppa__) \
> && !defined(__arm__) && !defined(CONFIG_V850) && !defined(__powerpc64__) \
> && !defined(__mips__)
How about just putting it into an a extra file and using lib-y in the Makefile?
Then it will be only linked when someone references it.
-Andi
next prev parent reply other threads:[~2004-05-19 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 9:49 [PATCH] fixing sendfile on 64bit architectures Andi Kleen
2004-05-19 12:21 ` Arnd Bergmann
2004-05-19 18:17 ` David Mosberger
2004-05-19 19:01 ` Andi Kleen [this message]
2004-05-19 19:13 ` David Mosberger
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 19:26 Arnd Bergmann
2004-05-20 6:19 ` David Mosberger
2004-05-20 6:41 ` 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=20040519210156.2a983a7c.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-arch@vger.kernel.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