All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin-l3A5Bk7waGM@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org,
	torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org
Subject: Re: [rfc] data race in page table setup/walking?
Date: Wed, 30 Apr 2008 08:17:42 +0200	[thread overview]
Message-ID: <20080430061741.GG27652@wotan.suse.de> (raw)
In-Reply-To: <20080429.230543.98200575.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

On Tue, Apr 29, 2008 at 11:05:43PM -0700, David Miller wrote:
> From: Nick Piggin <npiggin-l3A5Bk7waGM@public.gmane.org>
> Date: Wed, 30 Apr 2008 08:03:40 +0200
> 
> > Hardware walkers, I shouldn't worry too much about, except as a thought
> > exercise to realise that we have lockless readers. I think(?) alpha can
> > walk the linux ptes in hardware on TLB miss, but surely they will have
> > to do the requisite barriers in hardware too (otherwise things get
> > really messy)
> 
> My understanding is that all Alpha implementations walk the
> page tables in PAL code.

Ah OK. I guess that's effectively "hardware" as far as Linux is concerned.
I guess even x86 really walks the page tables in microcode as well. Basically
I just mean something that is invisible to, and obvlivious of, Linux's
locking.

 
> > Powerpc's find_linux_pte is one of the software walked lockless ones.
> > That's basically how I imagine hardware walkers essentially should operate.
> 
> Sparc64 walks the page tables lockless in it's TLB hash table miss
> handling.
> 
> MIPS does something similar.

Interesting, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: David Miller <davem@davemloft.net>
Cc: hugh@veritas.com, torvalds@linux-foundation.org,
	linux-arch@vger.kernel.org, linux-mm@kvack.org,
	benh@kernel.crashing.org
Subject: Re: [rfc] data race in page table setup/walking?
Date: Wed, 30 Apr 2008 08:17:42 +0200	[thread overview]
Message-ID: <20080430061741.GG27652@wotan.suse.de> (raw)
Message-ID: <20080430061742.U-FZ9QMUsHCXOvOg3pksbmSgUcnCxabw12v-eqd0m5I@z> (raw)
In-Reply-To: <20080429.230543.98200575.davem@davemloft.net>

On Tue, Apr 29, 2008 at 11:05:43PM -0700, David Miller wrote:
> From: Nick Piggin <npiggin@suse.de>
> Date: Wed, 30 Apr 2008 08:03:40 +0200
> 
> > Hardware walkers, I shouldn't worry too much about, except as a thought
> > exercise to realise that we have lockless readers. I think(?) alpha can
> > walk the linux ptes in hardware on TLB miss, but surely they will have
> > to do the requisite barriers in hardware too (otherwise things get
> > really messy)
> 
> My understanding is that all Alpha implementations walk the
> page tables in PAL code.

Ah OK. I guess that's effectively "hardware" as far as Linux is concerned.
I guess even x86 really walks the page tables in microcode as well. Basically
I just mean something that is invisible to, and obvlivious of, Linux's
locking.

 
> > Powerpc's find_linux_pte is one of the software walked lockless ones.
> > That's basically how I imagine hardware walkers essentially should operate.
> 
> Sparc64 walks the page tables lockless in it's TLB hash table miss
> handling.
> 
> MIPS does something similar.

Interesting, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: David Miller <davem@davemloft.net>
Cc: hugh@veritas.com, torvalds@linux-foundation.org,
	linux-arch@vger.kernel.org, linux-mm@kvack.org,
	benh@kernel.crashing.org
Subject: Re: [rfc] data race in page table setup/walking?
Date: Wed, 30 Apr 2008 08:17:42 +0200	[thread overview]
Message-ID: <20080430061741.GG27652@wotan.suse.de> (raw)
In-Reply-To: <20080429.230543.98200575.davem@davemloft.net>

On Tue, Apr 29, 2008 at 11:05:43PM -0700, David Miller wrote:
> From: Nick Piggin <npiggin@suse.de>
> Date: Wed, 30 Apr 2008 08:03:40 +0200
> 
> > Hardware walkers, I shouldn't worry too much about, except as a thought
> > exercise to realise that we have lockless readers. I think(?) alpha can
> > walk the linux ptes in hardware on TLB miss, but surely they will have
> > to do the requisite barriers in hardware too (otherwise things get
> > really messy)
> 
> My understanding is that all Alpha implementations walk the
> page tables in PAL code.

Ah OK. I guess that's effectively "hardware" as far as Linux is concerned.
I guess even x86 really walks the page tables in microcode as well. Basically
I just mean something that is invisible to, and obvlivious of, Linux's
locking.

 
> > Powerpc's find_linux_pte is one of the software walked lockless ones.
> > That's basically how I imagine hardware walkers essentially should operate.
> 
> Sparc64 walks the page tables lockless in it's TLB hash table miss
> handling.
> 
> MIPS does something similar.

Interesting, thanks.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-04-30  6:17 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29  5:00 [rfc] data race in page table setup/walking? Nick Piggin
2008-04-29  5:00 ` Nick Piggin
2008-04-29  5:00 ` Nick Piggin
     [not found] ` <20080429050054.GC21795-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2008-04-29  5:08   ` Benjamin Herrenschmidt
2008-04-29  5:08     ` Benjamin Herrenschmidt
2008-04-29  5:08     ` Benjamin Herrenschmidt
2008-04-29  5:41     ` Nick Piggin
2008-04-29  5:41       ` Nick Piggin
2008-04-29  5:41       ` Nick Piggin
2008-04-29 10:56   ` David Miller
2008-04-29 10:56     ` David Miller, Nick Piggin
2008-04-29 10:56     ` David Miller
2008-04-29 12:36   ` Hugh Dickins
2008-04-29 12:36     ` Hugh Dickins
2008-04-29 12:36     ` Hugh Dickins
     [not found]     ` <Pine.LNX.4.64.0804291333540.22025-popGQ1T0qN76K7/ahGyk6A@public.gmane.org>
2008-04-29 21:37       ` Benjamin Herrenschmidt
2008-04-29 21:37         ` Benjamin Herrenschmidt
2008-04-29 21:37         ` Benjamin Herrenschmidt
2008-04-29 22:47         ` Hugh Dickins
2008-04-29 22:47           ` Hugh Dickins
2008-04-29 22:47           ` Hugh Dickins
     [not found]           ` <Pine.LNX.4.64.0804292328110.23470-popGQ1T0qN76K7/ahGyk6A@public.gmane.org>
2008-04-30  0:09             ` Benjamin Herrenschmidt
2008-04-30  0:09               ` Benjamin Herrenschmidt
2008-04-30  0:09               ` Benjamin Herrenschmidt
2008-04-30  6:03       ` Nick Piggin
2008-04-30  6:03         ` Nick Piggin
2008-04-30  6:03         ` Nick Piggin
     [not found]         ` <20080430060340.GE27652-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2008-04-30  6:05           ` David Miller
2008-04-30  6:05             ` David Miller, Nick Piggin
2008-04-30  6:05             ` David Miller
     [not found]             ` <20080429.230543.98200575.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-04-30  6:17               ` Nick Piggin [this message]
2008-04-30  6:17                 ` Nick Piggin
2008-04-30  6:17                 ` Nick Piggin
2008-04-30 11:14           ` Hugh Dickins
2008-04-30 11:14             ` Hugh Dickins
2008-04-30 11:14             ` Hugh Dickins
     [not found]             ` <Pine.LNX.4.64.0804301140490.4651-popGQ1T0qN76K7/ahGyk6A@public.gmane.org>
2008-05-01  0:35               ` Nick Piggin
2008-05-01  0:35                 ` Nick Piggin
2008-05-01  0:35                 ` Nick Piggin
     [not found]                 ` <20080501003542.GB11312-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2008-05-01 12:45                   ` Hugh Dickins
2008-05-01 12:45                     ` Hugh Dickins
2008-05-01 12:45                     ` Hugh Dickins
2008-04-30 15:53           ` Linus Torvalds
2008-04-30 15:53             ` Linus Torvalds
2008-04-30 15:53             ` Linus Torvalds
     [not found]             ` <alpine.LFD.1.10.0804300848390.2997-5CScLwifNT1QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
2008-05-01  0:29               ` Nick Piggin
2008-05-01  0:29                 ` Nick Piggin
2008-05-01  0:29                 ` Nick Piggin
     [not found]                 ` <20080501002955.GA11312-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2008-05-01  3:24                   ` Linus Torvalds
2008-05-01  3:24                     ` Linus Torvalds
2008-05-01  3:24                     ` Linus Torvalds
2008-05-02  1:20                     ` Nick Piggin
2008-05-02  1:20                       ` Nick Piggin
2008-05-02  1:33                       ` Linus Torvalds
2008-05-02  1:33                         ` Linus Torvalds
2008-05-02  1:43                         ` Nick Piggin
2008-05-02  1:43                           ` Nick Piggin

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=20080430061741.GG27652@wotan.suse.de \
    --to=npiggin-l3a5bk7wagm@public.gmane.org \
    --cc=benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org \
    --cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.