linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Zoltan Menyhart <Zoltan.Menyhart@free.fr>
To: Hugh Dickins <hugh@veritas.com>, nickpiggin@yahoo.com.au
Cc: Zoltan Menyhart <Zoltan.Menyhart@bull.net>, linux-mm@kvack.org
Subject: Re: Any reason for passing "tlb" to "free_pgtables()" by address?
Date: Tue, 09 May 2006 21:30:18 +0200	[thread overview]
Message-ID: <4460EDCA.3000301@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.64.0605091207030.19410@blonde.wat.veritas.com>

Hugh, Nick,

Thank you for the information.

> Nick uses the pagetables themselves as buffering, I allocate a
> temporary buffer: in each case we abandon the per-cpu arrays which
> need preemption disabled.  But neither patch is good enough yet.

I'd like to note that the page table walking:

	TLB = ... -> pgd[i] -> pud[j] -> pmd[k] -> pte[l]

is not safe on some of the architectures which load TLB entries
"by hand", i.e. by use of some low level assembly routines,
e.g. IA64, Power.
Please refer to the thread "RFC: RCU protected page table walking".

Only some "careful programming" in the PUD / PMD / PTE page removal
code can help.
I propose a way to make sure that the page table walkers will be
able to finish their walks in safety; we release a directory page
when no more walker can reference the page.

Therefore I'd appreciate much a solution that would not use the
directory pages themselves as buffering. I'll need to preserve them
until the RCU based reclaim side.

Thanks,

Zoltan

--
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>

      reply	other threads:[~2006-05-09 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 10:53 Zoltan Menyhart
2006-05-05 12:41 ` Hugh Dickins
2006-05-08 21:50   ` Zoltan Menyhart
2006-05-09  1:40     ` Nick Piggin
2006-05-09 11:23     ` Hugh Dickins
2006-05-09 19:30       ` Zoltan Menyhart [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=4460EDCA.3000301@free.fr \
    --to=zoltan.menyhart@free.fr \
    --cc=Zoltan.Menyhart@bull.net \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    /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