linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org, hugh@veritas.com, paulus@samba.org,
	nickpiggin@yahoo.com.au, davem@davemloft.net
Subject: Re: vDSO vs. mm : problems with ppc vdso
Date: Tue, 28 Feb 2006 17:30:19 +1100	[thread overview]
Message-ID: <1141108220.3767.43.camel@localhost.localdomain> (raw)
In-Reply-To: <20060227222055.4d877f16.akpm@osdl.org>

> It should be done with some care - I suspect this will become *the*
> way in which we recognise a 64-bit mm and quite a bit of stuff will end up
> migrating to it.  We do need input from the various 64-bit people who have
> wrestled with these things.

Patch send, now let's get feedback ;)

> > I'll send the patch as a reply to this message.
> 
> Please copy linux-arch.

Did that.

> It's not ->mapping.  It's the fact that rmap only operates on pages which
> were found on the LRU.  If you don't add it to the LRU (and surely you do
> not) then no problem.

Ok.

> > Do you gus see any other case where my "special" vma & those kernel
> > pages in could be a problem ?
> 
> It sounds just like a sound card DMA buffer to me - that's a solved
> problem?  (Well, we keep unsolving it, but it's a relatively common
> pattern).

Might be ... though I though the later had VM_RESERVED or some similar
thing ... the trick with that vma is that i don't want any of these
things to allow for COW ... But yeah, it _looks_ like it will just work
(well... it appears to work so far anyway....)

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  6:30 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 [this message]
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
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=1141108220.3767.43.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