All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anthony DeRobertis" <asd@suespammers.org>
To: jtv <jtv@xs4all.nl>
Cc: Anthony DeRobertis <asd@suespammers.org>,
	Jacques Gelinas <jack@solucorp.qc.ca>,
	linux-kernel@vger.kernel.org
Subject: Re: Whizzy New Feature: Paged segmented memory
Date: Tue, 08 Jan 2002 14:05:09 GMT	[thread overview]
Message-ID: <E16NwsH-0005Ud-00@asd.ppp0.com> (raw)
In-Reply-To: <20020107224525.8a899969dbcd@remtk.solucorp.qc.ca> <BD98BECA-0407-11D6-804A-00039355CFA6@suespammers.org> <20020108122225.B11855@xs4all.nl>
In-Reply-To: <20020108122225.B11855@xs4all.nl>

jtv writes: 

> On Tue, Jan 08, 2002 at 02:17:14AM -0500, Anthony DeRobertis wrote:
>> 
>> A nice thing about two stacks is that it can be a completely 
>> userspace thing. No need to involve the kernel at all; just gcc 
>> and friends.
> 
> Doesn't it have ABI implications as well?

On every architecture I'm familiar with. But that's a userland issue. I 
don't believe the kernel cares how userland uses its stacks. 

Change gcc. Recompile world. All should work, assuming your gcc changes are 
bug-free, no one made assumptions about stack layout, no one wrote assembly 
code, etc. [In other words, after 4 months of debugging you might get X 
running again...] 

> 
> If so, why not go all the way and have stacks grow upwards?  :-)

Some architectures have hardware assistance for downward growing stacks. One 
example is 68K. I think x86 does too. OTOH, I don't think PPC does, though I 
haven't read the Green Book recently. 

Actually, if I were to be implementing split-stack, I'd probably have one 
grow upward. Probably the data stack, because some architectures (68K, at 
least) force the address stack to grow downwards. 

Put an unmapped page between the two stacks, and all should be fine. 

>  
> 
> Jeroen 
> 
 

  reply	other threads:[~2002-01-08 14:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08  3:45 Whizzy New Feature: Paged segmented memory Jacques Gelinas
2002-01-08  7:17 ` Anthony DeRobertis
2002-01-08 11:22   ` jtv
2002-01-08 14:05     ` Anthony DeRobertis [this message]
2002-01-08 14:14       ` Richard B. Johnson
2002-01-08 19:33         ` Anthony DeRobertis
2002-01-08 19:45           ` Richard B. Johnson
2002-01-08 17:11       ` jtv
2002-01-08 19:32         ` Anthony DeRobertis
  -- strict thread matches above, loose matches on Subject: below --
2002-01-08 13:42 Jacques Gelinas
2002-01-06 14:14 Marcin Tustin
2002-01-06 18:32 ` Gábor Lénárt
2002-01-06 20:41 ` Kevin Krieser

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=E16NwsH-0005Ud-00@asd.ppp0.com \
    --to=asd@suespammers.org \
    --cc=jack@solucorp.qc.ca \
    --cc=jtv@xs4all.nl \
    --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.