From: Ingo Molnar <mingo@elte.hu>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [UML] Performance hit for setting CS segment limit
Date: Tue, 15 Jun 2004 07:45:45 +0200 [thread overview]
Message-ID: <20040615054545.GB2543@elte.hu> (raw)
In-Reply-To: <200406111954.15283.blaisorblade_spam@yahoo.it>
* BlaisorBlade <blaisorblade_spam@yahoo.it> wrote:
> Hi Ingo, I need some help from you about the performance hit of
> segmentation, which you probably studied for the exec-shield patch.
>
> In short: if I reduce the limit of the CS, DS and so on segment
> descriptors (let's say it becomes 2,5G instead of 4G), a bit like you
> do in the exec-shield patch, will this setting impact on the
> performance of the process, apart for the time to set them? I also
> assume that segment changes do not flush the TLBs; is this correct?
>
> I've been told by Jeff Dike (you can check on the ML) that :
>
> "This is slow, plus ****using segments will cost you a cycle or
> something on EVERY memory reference***. Alan Cox warned me off very
> strongly against doing this.", though maybe he referred to something
> different: is this true in this case?
this might be true for _data_ segments, but not for the code segment.
The code segment limit can be checked when an iTLB miss occurs, no need
to check during code prefetch itself. So there's no overhead.
Ingo
-------------------------------------------------------
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 parent reply other threads:[~2004-06-15 5:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200406111954.15283.blaisorblade_spam@yahoo.it>
2004-06-15 5:45 ` Ingo Molnar [this message]
2004-06-16 19:41 ` [uml-devel] Re: [UML] Performance hit for setting CS segment limit BlaisorBlade
2004-06-18 5:49 ` Ingo Molnar
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=20040615054545.GB2543@elte.hu \
--to=mingo@elte.hu \
--cc=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