public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch 3/6] prefetch bottom of kernel rbs stack at syscall exit path
Date: Tue, 07 Feb 2006 21:27:32 +0000	[thread overview]
Message-ID: <200602072127.k17LRWg31633@unix-os.sc.intel.com> (raw)
In-Reply-To: <200601310913.k0V9DWg13193@unix-os.sc.intel.com>

David Mosberger-Tang wrote on Tuesday, February 07, 2006 1:19 PM
> > Chen, Kenneth wrote on Tuesday, January 31, 2006 11:27 AM
> > > David Mosberger-Tang wrote on Tuesday, January 31, 2006 9:45 AM
> > > > How much latency does this add for a minimal syscall when
> > > > everything is cached?
> > >
> > > I will get the measurement out shortly.
> >
> > Here are the numbers for break based getpid():
> >
> > Vanilla 2.6.15:    238 cycles
> > Vanilla + patches: 250 cycles
> 
> Hmmh, 12 cycles lost.  Can you see if you can do better?  There really
> are apps out there that care about this case (not getpid per se, but
> minimal syscall entry/exit overhead when everything is cached).

I'm with you completely on this.  I'm not happy with it either. So back
to the drawing board.

- Ken


      parent reply	other threads:[~2006-02-07 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  9:13 [patch 3/6] prefetch bottom of kernel rbs stack at syscall exit path Chen, Kenneth W
2006-01-31 17:44 ` David Mosberger-Tang
2006-01-31 19:27 ` Chen, Kenneth W
2006-02-07  2:56 ` Chen, Kenneth W
2006-02-07 21:19 ` David Mosberger-Tang
2006-02-07 21:27 ` Chen, Kenneth W [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=200602072127.k17LRWg31633@unix-os.sc.intel.com \
    --to=kenneth.w.chen@intel.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox