From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: The SKAS4 patch?? + ideas for 0 context-switch
Date: Mon, 14 Jun 2004 20:17:39 +0200 [thread overview]
Message-ID: <200406142017.39563.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200406092305.24447.blaisorblade_spam@yahoo.it>
Alle 23:05, mercoledì 9 giugno 2004, BlaisorBlade ha scritto:
> > plus using segments will cost you a cycle or something
> > on every memory reference.
The Intel Manual 3 (Intel System Programming Guide - 253668 -15.pdf) says, at
page 4-1 (page 107 in the PDF), that limit checking has no performance cost,
and I expect this to hold especially for simply verifying if an address is
below a limit. Maybe it could lie, ok, but maybe Alan Cox was referring to
more complex segmentation tricks.
I'm also going to ask to Ingo Molnar (he sets a segment limit in the CS
descriptor in his exec-shield patch, so he has probably benchmarked the
result).
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-06-15 3:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 17:49 [uml-devel] The SKAS4 patch?? + ideas for 0 context-switch BlaisorBlade
2004-06-08 4:55 ` [uml-devel] " Jeff Dike
2004-06-09 21:05 ` BlaisorBlade
2004-06-10 1:52 ` Jeff Dike
2004-06-14 18:17 ` BlaisorBlade [this message]
2004-06-14 18:10 ` BlaisorBlade
[not found] ` <200406121601.35801.blaisorblade_spam@yahoo.it>
2004-06-15 3:39 ` Jeff Dike
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=200406142017.39563.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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