From: Dave Hansen <dave.hansen@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Michal Hocko <mhocko@suse.com>
Cc: intel-gfx@lists.freedesktop.org, linux-mm@kvack.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Matthew Auld <matthew.auld@intel.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [RFC] mm,drm/i915: Mark pinned shmemfs pages as unevictable
Date: Tue, 6 Jun 2017 09:17:41 -0700 [thread overview]
Message-ID: <8774b0c2-ffc1-698a-e144-d0530cbd9382@intel.com> (raw)
In-Reply-To: <149675247191.14666.5385909547703846037@mail.alporthouse.com>
On 06/06/2017 05:34 AM, Chris Wilson wrote:
> With respect to i915, we may not be the sole owner of the page at the
> point where we call shmem_read_mapping_page_gfp() as it can mmapped or
> accessed directly via the mapping internally. It is just at this point
> we know that the page will not be returned to the system until we have
> finished using it with the GPU.
>
> An API that didn't assume the page was locked or require exclusive
> ownership would be needed for random driver usage like i915.ko
Why do you think exclusive ownership is required, btw? What does
exclusive ownership mean, anyway? page_count()==1 and you old the old
reference?
--
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>
next prev parent reply other threads:[~2017-06-06 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 12:04 [RFC] mm,drm/i915: Mark pinned shmemfs pages as unevictable Chris Wilson
2017-06-06 12:04 ` [RFC] mm, drm/i915: " Chris Wilson
2017-06-06 12:14 ` [RFC] mm,drm/i915: " Michal Hocko
2017-06-06 12:14 ` [RFC] mm, drm/i915: " Michal Hocko
2017-06-06 12:30 ` [RFC] mm,drm/i915: " Vlastimil Babka
2017-06-06 14:05 ` Chris Wilson
2017-06-06 17:47 ` Jerome Glisse
2017-06-06 17:47 ` Jerome Glisse
2017-06-06 12:34 ` Chris Wilson
2017-06-06 16:17 ` Dave Hansen [this message]
2017-06-06 16:17 ` Dave Hansen
2017-06-06 16:23 ` Peter Zijlstra
2017-08-19 13:15 ` Chris Wilson
2017-08-21 14:06 ` Michal Hocko
2017-08-21 15:03 ` Chris Wilson
2017-08-21 15:57 ` Peter Zijlstra
2017-08-21 15:57 ` [RFC] mm, drm/i915: " Peter Zijlstra
2017-08-21 16:29 ` [RFC] mm,drm/i915: " Christopher Lameter
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=8774b0c2-ffc1-698a-e144-d0530cbd9382@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=matthew.auld@intel.com \
--cc=mhocko@suse.com \
--cc=peterz@infradead.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.