From: Arnd Bergmann <arnd@arndb.de>
To: Chris Friesen <chris.friesen@genband.com>
Cc: David Miller <davem@davemloft.net>,
eric.dumazet@gmail.com, netdev@vger.kernel.org
Subject: Re: [RFC] should we care of COMPAT mode in bridge ?
Date: Mon, 6 Jun 2011 22:31:32 +0200 [thread overview]
Message-ID: <201106062231.32226.arnd@arndb.de> (raw)
In-Reply-To: <4DED3759.7030209@genband.com>
On Monday 06 June 2011 22:23:53 Chris Friesen wrote:
> It raises an interesting question though...do we plan on supporting
> compat indefinitely?
>
> As I see it x86 generally makes more sense to run as 64-bit when
> possible due to the extra register availability. Compat is primarily
> useful for the embedded space and for backwards compatibility, and
> ripping it out would cause a lot of grief for legacy 32-bit apps. It
> would simplify the userspace/kernel interface though.
There are a lot of applications that require being run as 32 bit,
and some of them are much happier in a chroot environment. Removing
the compat support entirely won't be an option for the next 10 years
at least, AFAICT. Even if we get all x86 folks to migrate to 64 bits
at some point in the distant future, there will always be other
architectures that make the move to 64 bits.
Note that there is currently work going on to add a new x32 ABI
to arch/x86 which makes it possible to use 32 bit pointers with the
full 64 bit register set. If this becomes a success, we will never
be able to build x86 kernels without compat support.
Arnd
next prev parent reply other threads:[~2011-06-06 20:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 19:45 [RFC] should we care of COMPAT mode in bridge ? Eric Dumazet
2011-06-06 20:03 ` David Miller
2011-06-06 20:23 ` Chris Friesen
2011-06-06 20:31 ` Arnd Bergmann [this message]
2011-06-06 20:31 ` Andreas Schwab
2011-06-06 20:34 ` Eric Dumazet
2011-06-07 23:51 ` Stephen Hemminger
2011-06-08 0:27 ` David Miller
2011-06-08 16:08 ` Stephen Hemminger
2011-06-06 20:06 ` Arnd Bergmann
2011-06-06 20:09 ` David Miller
2011-06-06 20:19 ` Arnd Bergmann
2011-06-06 20:23 ` David Miller
2011-06-07 23:54 ` Stephen Hemminger
2011-06-06 20:12 ` Eric Dumazet
2011-06-06 20:26 ` Arnd Bergmann
2011-06-06 20:32 ` Eric Dumazet
2011-06-06 20:33 ` Arnd Bergmann
2011-06-06 20:35 ` Eric Dumazet
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=201106062231.32226.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=chris.friesen@genband.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@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).