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: Prefetch mmap_sem in ia64_do_page_fault()
Date: Wed, 29 Mar 2006 07:31:42 +0000	[thread overview]
Message-ID: <200603290730.k2T7Uug04138@unix-os.sc.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603282251410.20180@schroedinger.engr.sgi.com>

Christoph Lameter wrote on Tuesday, March 28, 2006 11:16 PM
> > If you insist on prefetching mmap_sem at the very beginning of the
> > function, then use speculative load, it will "nat" right away with
> > null pointer without generating any exception at all.  It is super
> > fast because of nat page.
> 
> I saw David Mosberger's patch from last year
> 
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hE8f935527372499b714bf4f8e646a68bb0f52e3
> 
> and it seems that he implemented fast handling of these NULL cases?

I know about that patch and I'm referring in the context of that commit:

ld8.s r1=[r0]      - immediate nat generation, no fault
lfetch.fault [r0]  - generate nat page consumption because lfetch is not
                     considered as a speculative access.

The nat page consumption fault handler should be rather quick, though cpu
still have to fault into the handler, muck around with ipsr.ed bit and
then rfi.  What I'm saying is there is an even *faster* way of doing
prefetch.

> mm = NULL is very rare so I think we can try to prefetch as 
> early as possible.

Yeah, sure. Looks good!

- Ken

  parent reply	other threads:[~2006-03-29  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29  6:54 Prefetch mmap_sem in ia64_do_page_fault() Christoph Lameter
2006-03-29  7:11 ` Chen, Kenneth W
2006-03-29  7:16 ` Christoph Lameter
2006-03-29  7:31 ` Chen, Kenneth W [this message]
2006-03-29  7:44 ` Chen, Kenneth W
2006-03-30  2:06 ` Christoph Lameter

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=200603290730.k2T7Uug04138@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