linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
From: Nick Piggin <npiggin@suse.de>
To: npiggin@suse.de
Cc: akpm@linux-foundation.org, shaggy@austin.ibm.com,
	axboe@oracle.com, linux-mm@kvack.org, linux-arch@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: [patch 1/2]: x86: implement pte_special
Date: Thu, 27 Mar 2008 21:16:32 -0700 (PDT)
Date: Fri, 28 Mar 2008 05:15:20 +0100	[thread overview]
Message-ID: <20080327.211632.02770342.davem@davemloft.net> (raw)
In-Reply-To: <20080328041519.GF8083@wotan.suse.de>

> The other thing is that the "how do I know if I can refcount the page
> behind this (mm,vaddr,pte) tuple" can be quite arch specific as well.
> And it is also non-trivial to do because that information can be dynamic
> depending on what driver mapped in that given tuple.

Those are good points.

--
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:[~2008-03-28  4:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28  2:54 [patch 0/2]: lockless get_user_pages patchset Nick Piggin
2008-03-28  2:55 ` [patch 1/2]: x86: implement pte_special Nick Piggin
2008-03-28  3:23   ` David Miller, Nick Piggin
2008-03-28  3:31     ` Nick Piggin
2008-03-28  3:44       ` David Miller, Nick Piggin
2008-03-28  4:04         ` Nick Piggin
2008-03-28  4:09           ` David Miller, Nick Piggin
2008-03-28  4:15             ` Nick Piggin
2008-03-28  4:16               ` David Miller, Nick Piggin [this message]
2008-03-28  4:19                 ` Nick Piggin
2008-03-28  4:17               ` Nick Piggin
2008-03-28  3:00 ` [patch 2/2]: introduce fast_gup Nick Piggin
2008-03-28 10:01   ` Jens Axboe
2008-04-17 15:03   ` Peter Zijlstra
2008-04-17 15:25     ` Linus Torvalds
2008-04-17 16:12       ` Peter Zijlstra
2008-04-17 16:18         ` Linus Torvalds
2008-04-17 16:35           ` Peter Zijlstra
2008-04-17 16:40             ` Linus Torvalds
2008-04-17 17:23               ` Peter Zijlstra
2008-04-17 18:28                 ` Linus Torvalds
2008-04-22  3:14                   ` Nick Piggin
2008-04-18  6:31                 ` Geert Uytterhoeven
2008-04-18 14:40                   ` Linus Torvalds
2008-04-18  9:58         ` Jeremy Fitzhardinge
2008-04-21 12:00       ` Avi Kivity
2008-04-21 12:30         ` Peter Zijlstra
2008-04-21 13:26           ` Avi Kivity
2008-04-21 14:35             ` Peter Zijlstra
2008-04-22  3:23               ` Nick Piggin
2008-04-22  7:19                 ` Avi Kivity
2008-04-22  8:07                 ` Ingo Molnar
2008-04-22  9:42   ` Peter Zijlstra
2008-04-22  9:46     ` Nick Piggin
2008-05-14 18:33       ` Dave Kleikamp
2008-05-15  1:13         ` Nick Piggin
  -- strict thread matches above, loose matches on Subject: below --
2008-05-21 11:59 [patch 1/2] x86: implement pte_special Nick Piggin
2008-05-25 14:48 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=20080327.211632.02770342.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@oracle.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=shaggy@austin.ibm.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).