linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Andrew Morton <akpm@osdl.org>,
	linux-mm@kvack.org, paulus@samba.org, davem@davemloft.net
Subject: Re: vDSO vs. mm : problems with ppc vdso
Date: Wed, 01 Mar 2006 04:55:54 +1100	[thread overview]
Message-ID: <1141149355.3767.57.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0602281213540.7059@goblin.wat.veritas.com>

On Tue, 2006-02-28 at 12:32 +0000, Hugh Dickins wrote:
> On Tue, 28 Feb 2006, Nick Piggin wrote:
> > 
> > You should be OK. VM_RESERVED itself is something of an anachronism
> > these days. If you're not getting your page from the page allocator
> > then you'll want to make sure each of their count, and mapcount is
> > reset before allowing them to be mapped.
> 
> Yes, it's fine that VM_RESERVED isn't set on it.
> But I don't understand your remarks about count and mapcount at all:
> perhaps you meant to say something else?

Ah thanks , I was worried there too ;)

> If I ignore what you actually said, and think of what problems there
> might be in that area, then yes, if the pages come from kernel memory
> (they do) rather than page allocator, we'd better make sure page_count
> starts above 0, so it doesn't go down to zero on last free from userspace:
> and indeed, Ben's vdso_init does a get_page on each to ensure that.

Yup, I took care of that and that part seems to work. I don't touch
mapcount at all.

Ben.


--
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-02-28 17:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28  5:39 Benjamin Herrenschmidt
2006-02-28  5:54 ` Andrew Morton
2006-02-28  6:08   ` Benjamin Herrenschmidt
2006-02-28  6:20     ` Andrew Morton
2006-02-28  6:30       ` Benjamin Herrenschmidt
2006-02-28  6:47         ` Andrew Morton
2006-02-28  7:36           ` Benjamin Herrenschmidt
2006-02-28 12:13           ` Hugh Dickins
2006-02-28 10:24         ` Nick Piggin
2006-02-28 12:32           ` Hugh Dickins
2006-02-28 17:55             ` Benjamin Herrenschmidt [this message]
2006-03-01  2:24             ` Nick Piggin
2006-03-01  2:26               ` Benjamin Herrenschmidt
2006-03-01  2:38                 ` Nick Piggin
2006-02-28  6:27     ` [PATCH] Add mm->task_size and fix powerpc vdso Benjamin Herrenschmidt

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=1141149355.3767.57.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=paulus@samba.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