From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: David Newall <davidn@davidnewall.com>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for mm] Remove iBCS support
Date: Sun, 20 Jan 2008 13:51:12 +0000 [thread overview]
Message-ID: <20080120135112.7bc317c7@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <47934FF5.4010904@davidnewall.com>
> Well, I'm whispering: The cost is that something desirable but
> incomplete would be removed. While it's there it's a constant source of
> irritation to those in the know. Once removed it can be forgotten. So
> the cost is really that iBCS2 compatibility becomes less likely. What's
> the benefit in removing it? Up to 20 cycles per exec? That's nothing.
Well you whispered many years too late. iBCS support vanished in 2.4
because nobody cared, nobody wanted to maintain it and not a single
vendor saw a business demand to justify assigning someone to do any work
with it.
If you want it back then you need to port the 2.4 iBCS emulation layer
code to 2.6 first. Of course you could probably also do it all in user
space with some LD_PRELOAD work and binfmt_misc. That might be a bit
slower but a lot more portable.
Alan
next prev parent reply other threads:[~2008-01-20 13:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 4:59 [PATCH for mm] Remove iBCS support Andi Kleen
2008-01-20 2:27 ` David Newall
2008-01-20 3:11 ` Andi Kleen
2008-01-20 4:46 ` David Newall
2008-01-20 5:18 ` Andi Kleen
2008-01-20 5:33 ` David Newall
2008-01-20 5:55 ` Andi Kleen
2008-01-20 6:23 ` David Newall
2008-01-20 7:29 ` Andi Kleen
2008-01-21 1:37 ` David Newall
2008-01-22 10:24 ` Karl Kiniger
2008-01-22 15:06 ` David Newall
2008-01-22 15:52 ` Adrian Bunk
2008-01-23 8:48 ` Andi Kleen
2008-01-23 14:12 ` Karl Kiniger
2008-01-23 14:24 ` Andi Kleen
2008-01-24 17:06 ` David Newall
2008-01-22 11:12 ` Ingo Molnar
2008-01-22 12:42 ` Karl Kiniger
2008-01-22 15:13 ` David Newall
2008-01-22 15:49 ` Ingo Molnar
2008-01-24 17:01 ` David Newall
2008-01-22 16:01 ` Adrian Bunk
2008-01-24 17:04 ` David Newall
2008-01-24 17:24 ` Adrian Bunk
2008-01-24 17:55 ` David Newall
2008-01-24 18:14 ` Adrian Bunk
2008-01-25 2:14 ` David Newall
2008-01-25 5:12 ` Valdis.Kletnieks
2008-01-25 16:40 ` Alan Cox
2008-01-24 19:51 ` Pavel Machek
2008-01-25 2:17 ` David Newall
2008-01-24 20:37 ` Andi Kleen
2008-01-25 2:16 ` David Newall
2008-01-22 16:50 ` Alan Cox
2008-01-24 17:08 ` David Newall
2008-01-22 13:20 ` Giulio
2008-01-20 13:06 ` Alan Cox
2008-01-20 13:43 ` David Newall
2008-01-20 13:51 ` Alan Cox [this message]
2008-01-25 12:17 ` Ingo Molnar
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=20080120135112.7bc317c7@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=davidn@davidnewall.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 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).