From: Ingo Molnar <mingo@elte.hu>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [UML] Performance hit for setting CS segment limit
Date: Fri, 18 Jun 2004 07:49:54 +0200 [thread overview]
Message-ID: <20040618054954.GA13608@elte.hu> (raw)
In-Reply-To: <200406162141.57213.blaisorblade_spam@yahoo.it>
* BlaisorBlade <blaisorblade_spam@yahoo.it> wrote:
> >, but not for the code segment.
> > The code segment limit can be checked when an iTLB miss occurs
>
> And so iTLB means instruction TLB, right? (I was wondering about this
> in your discussion about 4G/4G patch with Andrea Arcangeli).
yeah.
> Also, from some tests, I would guess that also for Celeron, and not
> only for Xeon, there are at least 64 dTLB. Is this correct? I used
> this to explain some benchmark datas.
'x86info -c' will tell you precisely how many TLBs there are for each
type.
> I noticed that when touching more than 64 different pages (i.e. 512 in
> my test), flushing or not the TLBs gave almost no "secondary cost" for
> reloading them when re-touching those pages, while the secondary cost
> was very high with 64 pages.
yes, there are such boundaries. (they are often not precisely at 64
pages because code also needs a stack and maybe global variables, but
generally it's around the # of dTLBs.)
> >, no need
> > to check during code prefetch itself. So there's no overhead.
>
> The only difference, here, is that for data segments, which are also
> important here, on a dTLB (i.e. I guess dTLB = data TLB) fault the
> check is done for a certain segment, so it could have a little
> overhead (though Intel claims it is done in parallel with address
> translation, in their manuals).
it depends on the CPU. But generally the more modern an x86 CPU is, the
higher the relative penalty for any segmentation trick ... and this
trend wont stop in the future i'm afraid.
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
prev parent reply other threads:[~2004-06-18 5:48 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 ` [uml-devel] Re: [UML] Performance hit for setting CS segment limit Ingo Molnar
2004-06-16 19:41 ` BlaisorBlade
2004-06-18 5:49 ` Ingo Molnar [this message]
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=20040618054954.GA13608@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