All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Hugh Dickins <hughd@google.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Steve Capper <steve.capper@linaro.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH] mm: get page_cache_get_speculative() work on tail pages
Date: Thu, 2 Apr 2015 15:09:05 +0300	[thread overview]
Message-ID: <20150402120905.GD24028@node.dhcp.inet.fi> (raw)
In-Reply-To: <alpine.LSU.2.11.1504011705310.6939@eggly.anvils>

On Wed, Apr 01, 2015 at 05:08:53PM -0700, Hugh Dickins wrote:
> On Thu, 2 Apr 2015, Kirill A. Shutemov wrote:
> > On Wed, Apr 01, 2015 at 04:21:30PM -0700, Hugh Dickins wrote:
> > > On Thu, 2 Apr 2015, Kirill A. Shutemov wrote:
> > > 
> > > > Generic RCU fast GUP rely on page_cache_get_speculative() to obtain pin
> > > > on pte-mapped page.  As pointed by Aneesh during review of my compound
> > > > pages refcounting rework, page_cache_get_speculative() would fail on
> > > > pte-mapped tail page, since tail pages always have page->_count == 0.
> > > > 
> > > > That means we would never be able to successfully obtain pin on
> > > > pte-mapped tail page via generic RCU fast GUP.
> > > > 
> > > > But the problem is not exclusive to my patchset. In current kernel some
> > > > drivers (sound, for instance) already map compound pages with PTEs.
> > > 
> > > Hah, you were sending this as I was replying to the original thread.
> > > 
> > > Do we care if fast gup fails on some hardware driver's compound pages?
> > > I don't think we do, and it would be better not to complicate the
> > > low-level page_cache_get_speculative for them.
> > 
> > Fair enough :-/
> > 
> > I'll check tomorrow if it will look more reasonable on gup_pte_range()
> > level, rather than page_cache_get_speculative().
> 
> But we don't need it on the (fast) gup_pte_range() level either, do we?
> Or do you have THP changes in mmotm which are now demanding this?

No. I'll keep it local to my patchset.

-- 
 Kirill A. Shutemov

--
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:[~2015-04-02 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 22:52 [PATCH] mm: get page_cache_get_speculative() work on tail pages Kirill A. Shutemov
2015-04-01 23:21 ` Hugh Dickins
2015-04-01 23:56   ` Kirill A. Shutemov
2015-04-02  0:08     ` Hugh Dickins
2015-04-02 12:09       ` Kirill A. Shutemov [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=20150402120905.GD24028@node.dhcp.inet.fi \
    --to=kirill@shutemov.name \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=steve.capper@linaro.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.