From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: FW: [patch 1/6] remove dead code in ia64_leave_kernel
Date: Tue, 31 Jan 2006 19:48:02 +0000 [thread overview]
Message-ID: <200601311948.k0VJmAg03598@unix-os.sc.intel.com> (raw)
In-Reply-To: <200601310907.k0V976g12698@unix-os.sc.intel.com>
I just did a reply on the original mail. Forwarding my response.
-----Original Message-----
From: Chen, Kenneth W [mailto:kenneth.w.chen@intel.com]
Sent: Tuesday, January 31, 2006 11:42 AM
To: 'David Mosberger-Tang'
Subject: RE: [patch 1/6] remove dead code in ia64_leave_kernel
David Mosberger-Tang wrote on Tuesday, January 31, 2006 9:51 AM
> Be careful here. Signal-delivery triggers some strange corner-cases.
> I don't have this all in my head at the moment, but one tricky part is
> returning from a signal-handler, where you enter the kernel as a
> syscall, but leave it as a non-syscall (usually). I trust that you
> already checked this case, but wanted to make sure the point isn't
> lost.
Thanks for the warning, I don't think I checked that corner case. I will
look at it again.
> Also, I believe with your patch, you'll end up consuming the read of
> ar.bsp which could adversely affect the latency of syscalls
> (especially when everything is cached). Did you check on this?
Kernel currently consumes the read of ar.bsp, since it has to preserve
the current frame, and it does so by doing two ar.bsp read: once before
cover instruction, and once after to calculate new ndirty value to be
loaded into ar.rsc. I'm not changing the order or location of these
ar.bsp reads in this patch. The code that I moved are always executed
for syscall leave.
Having said that, I have a craze idea of optimize away two bsp reads
along with cover instruction in the syscall leave path. I'm still
exploring whether that is achievable or not. If we can do that, then
all that latency would go away along with the code that this patch moved.
- Ken
next prev parent reply other threads:[~2006-01-31 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 9:06 [patch 1/6] remove dead code in ia64_leave_kernel Chen, Kenneth W
2006-01-31 19:48 ` Chen, Kenneth W [this message]
2006-02-01 3:12 ` FW: " David Mosberger-Tang
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=200601311948.k0VJmAg03598@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