From: Christoph Hellwig <hch@infradead.org>
To: davidm@hpl.hp.com
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixing sendfile on 64bit architectures
Date: Thu, 20 May 2004 20:35:32 +0100 [thread overview]
Message-ID: <20040520203532.A11902@infradead.org> (raw)
In-Reply-To: <16557.1651.307484.282000@napali.hpl.hp.com>; from davidm@napali.hpl.hp.com on Thu, May 20, 2004 at 12:26:43PM -0700
On Thu, May 20, 2004 at 12:26:43PM -0700, David Mosberger wrote:
> Andrew,
>
> Below is a patch that tries to sanitize the dropping of unneeded
> system-call stubs in generic code. In some instances, it would be
> possible to move the optional system-call stubs into a library routine
> which would avoid the need for #ifdefs, but in many cases, doing so
> would require making several functions global (and possibly exporting
> additional data-structures in header-files). Furthermore, it would
> inhibit (automatic) inlining in the cases in the cases where the stubs
> are needed. For these reasons, the patch keeps the #ifdef-approach.
>
> This has been tested on ia64 and there were no objections from the
> arch-maintainers (and one positive response). The patch should be
> safe but arch-maintainers may want to take a second look to see if
> additional __ARCH_OMIT_foo macros should be turned on for their
> architecture (I'm quite sure that's the case, but I wanted to play it
> safe and only preserved the status-quo in that regard).
IMHO this is exactly the wrong way around. It should be __ARCH_WANT_*
or something like that so new architectures don't carry the old garbage
around by default. There's far too many new architectures keeping old
syscalls by accident.
next prev parent reply other threads:[~2004-05-20 19:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 19:26 [PATCH] fixing sendfile on 64bit architectures Arnd Bergmann
2004-05-20 6:19 ` David Mosberger
2004-05-20 6:41 ` David S. Miller
[not found] ` <16556.65456.624986.552865@napali.hpl.hp.com>
[not found] ` <20040520120645.3accf048.akpm@osdl.org>
2004-05-20 19:26 ` David Mosberger
2004-05-20 19:35 ` Christoph Hellwig [this message]
2004-05-20 20:17 ` David Mosberger
2004-05-20 21:56 ` Andrew Morton
2004-05-20 22:00 ` David Mosberger
2004-05-20 22:09 ` David Mosberger
2004-05-20 23:30 ` Andrew Morton
2004-05-20 23:44 ` David Mosberger
2004-05-21 0:17 ` Spam: " Andrew Morton
2004-05-21 0:25 ` David Mosberger
2004-05-20 22:10 ` Jesse Barnes
2004-05-20 22:25 ` Andrew Morton
2004-05-20 22:32 ` David Mosberger
2004-05-20 22:33 ` Jesse Barnes
2004-05-23 9:37 ` Geert Uytterhoeven
[not found] <1Y1yE-4Lz-7@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-9@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-11@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-13@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-15@gated-at.bofh.it>
[not found] ` <1Y1yE-4Lz-5@gated-at.bofh.it>
[not found] ` <1Y1yJ-4Lz-37@gated-at.bofh.it>
[not found] ` <1Y2l5-5rr-5@gated-at.bofh.it>
[not found] ` <1Y3Ki-6x6-35@gated-at.bofh.it>
2004-05-21 9:01 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 9:49 Andi Kleen
2004-05-19 12:21 ` Arnd Bergmann
2004-05-19 18:17 ` David Mosberger
2004-05-19 19:01 ` Andi Kleen
2004-05-19 19:13 ` 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=20040520203532.A11902@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.