Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: akash.goel@intel.com, intel-gfx@lists.freedesktop.org,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Hugh Dickins <hughd@google.com>,
	linux-mm@kvack.org, Sourab Gupta <sourab.gupta@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] drm/i915: Make GPU pages movable
Date: Wed, 9 Nov 2016 10:36:06 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.11.1611091034470.1547@eggly.anvils> (raw)
In-Reply-To: <20161109112835.kivhola7ux3lw4s6@phenom.ffwll.local>

On Wed, 9 Nov 2016, Daniel Vetter wrote:
> 
> Hi all -mm folks!
> 
> Any feedback on these two? It's kinda an intermediate step towards a
> full-blown gemfs, and I think useful for that. Or do we need to go
> directly to our own backing storage thing? Aside from ack/nack from -mm I
> think this is ready for merging.

I'm currently considering them at last: will report back later.

Full-blown gemfs does not come in here, of course; but let me
fire a warning shot since you mention it: if it's going to use swap,
then we shall probably have to nak it in favour of continuing to use 
infrastructure from mm/shmem.c.  I very much understand why you would
love to avoid that dependence, but I doubt it can be safely bypassed.

Hugh

--
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:[~2016-11-09 18:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 15:02 [PATCH 1/2] shmem: Support for registration of driver/file owner specific ops akash.goel
2016-11-04 15:02 ` [PATCH 2/2] drm/i915: Make GPU pages movable akash.goel
2016-11-09 11:28   ` Daniel Vetter
2016-11-09 18:36     ` Hugh Dickins [this message]
2016-11-22 16:02       ` [Intel-gfx] " Matthew Auld
2016-11-23  5:26         ` Hugh Dickins
2016-11-23  8:36           ` Daniel Vetter
2016-11-23 19:00             ` Hugh Dickins
2016-11-10  6:39   ` Hugh Dickins
2016-11-10  7:30     ` Goel, Akash
2016-11-14  7:57       ` akash goel
2016-11-16  1:25         ` Hugh Dickins
2016-11-16  5:13           ` akash goel
2016-11-10  5:36 ` [PATCH 1/2] shmem: Support for registration of driver/file owner specific ops Hugh Dickins
2016-11-10 16:22   ` Goel, Akash
2016-11-11 13:50     ` Chris Wilson
  -- strict thread matches above, loose matches on Subject: below --
2016-10-20 15:15 [Intel-gfx] [PATCH 1/2] shmem: Support for registration of Driver/file " Joonas Lahtinen
2016-11-04 12:48 ` [PATCH 1/2] shmem: Support for registration of driver/file " akash.goel
2016-11-04 12:48   ` [PATCH 2/2] drm/i915: Make GPU pages movable akash.goel
2016-11-04 13:37     ` Chris Wilson
2016-11-04 13:53       ` Goel, Akash

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=alpine.LSU.2.11.1611091034470.1547@eggly.anvils \
    --to=hughd@google.com \
    --cc=akash.goel@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-mm@kvack.org \
    --cc=sourab.gupta@intel.com \
    /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