From: Jacques Gelinas <jack@solucorp.qc.ca>
To: <linux-kernel@vger.kernel.org>
Subject: re: Whizzy New Feature: Paged segmented memory
Date: Mon, 7 Jan 2002 22:45:25 -0500 [thread overview]
Message-ID: <20020107224525.8a899969dbcd@remtk.solucorp.qc.ca> (raw)
On Sun, 6 Jan 2002 14:14:30 -0500, Marcin Tustin wrote
>
> Any comments on how useful it would be to have paged, segmented,
> memory support for Pentium? I was thinking that by having separate
> segments for text, stack, and heap, buffer overrun exploits would be
> eliminated (I'm aware that this would require GCC patching as well).
> Obviously, I'm thinking that I (and any similar fools I could rope
> in) would try this (Probably delivering for a kernel at least a year out
> of date by the time we had a patch).
Another solution would be to have two stacks. One for variable (auto data)
and one for program execution (call). Beside cache effect, this would provide
mostly the same performance as we get now. Just wondering if someone had
toyed with this idea.
---------------------------------------------------------
Jacques Gelinas <jack@solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc
next reply other threads:[~2002-01-08 5:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 3:45 Jacques Gelinas [this message]
2002-01-08 7:17 ` Whizzy New Feature: Paged segmented memory Anthony DeRobertis
2002-01-08 11:22 ` jtv
2002-01-08 14:05 ` Anthony DeRobertis
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=20020107224525.8a899969dbcd@remtk.solucorp.qc.ca \
--to=jack@solucorp.qc.ca \
--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.