From: William Lee Irwin III <wli@holomorphy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Roland Dreier <roland@topspin.com>,
jmerkey@comcast.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jmerkey@drdos.com
Subject: Re: 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM)
Date: Sun, 29 Aug 2004 09:42:39 -0700 [thread overview]
Message-ID: <20040829164239.GH5492@holomorphy.com> (raw)
In-Reply-To: <1093783694.27899.7.camel@localhost.localdomain>
On Iau, 2004-08-26 at 05:49, William Lee Irwin III wrote:
>> Though asinine, the ABI spec is set in stone.
On Sun, Aug 29, 2004 at 01:48:14PM +0100, Alan Cox wrote:
> Lots of Linux configuration options build you systems that don't meet
> some specifications. "Intentionally violate a stupid spec to get work
> done" is a good option 8)
The big nasty is that userspace has very little to go on here. We need
to report the limits of the address space somewhere for this kind of
affair and probably even hammer out our own addenda to ABI specs so
instead of SVR4 $ARCH/ELF ABI spec we have a Linux $ARCH/ELF ABI spec.
I see no one so motivated to make backward-incompatible ABI changes
that they are willing to do that kind of work.
-- wli
next prev parent reply other threads:[~2004-08-29 16:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 4:21 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM) jmerkey
2004-08-26 4:33 ` William Lee Irwin III
2004-08-26 4:46 ` Roland Dreier
2004-08-26 4:49 ` William Lee Irwin III
2004-08-26 8:40 ` Ryan Cumming
2004-08-29 12:48 ` Alan Cox
2004-08-29 16:42 ` William Lee Irwin III [this message]
2004-08-29 15:45 ` Alan Cox
2004-08-29 17:00 ` William Lee Irwin III
2004-08-26 4:38 ` Martin J. Bligh
2004-08-26 4:42 ` Roland Dreier
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 20:24 jmerkey
2004-08-26 20:38 ` William Lee Irwin III
2004-08-26 21:41 ` Dave Jones
2004-08-26 21:08 jmerkey
2004-08-26 21:43 ` William Lee Irwin III
2004-08-26 23:47 linux
2004-08-30 4:01 jmerkey
2004-08-30 4:35 ` Randy.Dunlap
2004-08-30 5:56 jmerkey
2004-08-30 18:10 ` Randy.Dunlap
2004-08-30 18:28 ` Roland Dreier
2004-09-22 18:52 ` Timothy Miller
2004-09-22 18:51 ` Roland Dreier
2004-09-22 20:22 ` Timothy Miller
2004-09-27 14:55 ` Roland Dreier
2004-08-31 22:50 jmerkey
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=20040829164239.GH5492@holomorphy.com \
--to=wli@holomorphy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jmerkey@comcast.net \
--cc=jmerkey@drdos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@topspin.com \
/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