linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Gioh Kim <gioh.kim@lge.com>, Dave Airlie <airlied@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	jlayton@poochiereds.net, bfields@fieldses.org, vbabka@suse.cz,
	iamjoonsoo.kim@lge.com, Al Viro <viro@zeniv.linux.org.uk>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	koct9i@gmail.com, minchan@kernel.org, aquini@redhat.com,
	linux-fsdevel@vger.kernel.org, "open list:VIRTIO CORE,
	NET..." <virtualization@lists.linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	open@kvack.org, list@kvack.org,
	ABI/API <linux-api@vger.kernel.org>,
	Linux Memory Management List <linux-mm@kvack.org>,
	gunho.lee@lge.com, Gioh Kim <gurugio@hanmail.net>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [RFCv3 0/5] enable migration of driver pages
Date: Thu, 9 Jul 2015 16:33:01 +0300	[thread overview]
Message-ID: <20150709133301.GG5176@intel.com> (raw)
In-Reply-To: <20150709130848.GD21858@phenom.ffwll.local>

On Thu, Jul 09, 2015 at 03:08:48PM +0200, Daniel Vetter wrote:
> On Thu, Jul 09, 2015 at 08:55:25AM +0900, Gioh Kim wrote:
> > 
> > 
> > 2015-07-09 오전 7:47에 Dave Airlie 이(가) 쓴 글:
> > >>>
> > >>>
> > >>>Can the various in-kernel GPU drivers benefit from this?  If so, wiring
> > >>>up one or more of those would be helpful?
> > >>
> > >>
> > >>I'm sure that other in-kernel GPU drivers can have benefit.
> > >>It must be helpful.
> > >>
> > >>If I was familiar with other in-kernel GPU drivers code, I tried to patch
> > >>them.
> > >>It's too bad.
> > >
> > >I'll bring dri-devel into the loop here.
> > >
> > >ARM GPU developers please take a look at this stuff, Laurent, Rob,
> > >Eric I suppose.
> > 
> > I sent a patch, https://lkml.org/lkml/2015/3/24/1182, and my opinion about compaction
> > to ARM GPU developers via Korea ARM branch.
> > I got a reply that they had no time to review it.
> > 
> > I hope they're interested to this patch.
> 
> i915 gpus would support 64kb and 2mb pages, but we never implemented this.
> I don't think this would fit for gem based drivers since our backing
> storage is shmemfs. So if we want to implement page migration (which we'd
> probably want to make large pages work well) we'd need to pimp shmem to a)
> hand large pages to us b) forward the migrate calls. Probably that means
> we need to build our own gemfs reusing shmemfs code.

AFAIK there are efforts ongoing to make large pages work with shmem.

Kirill, IIRC you mentioned that you're were looking into this a while
back?

-- 
Ville Syrjälä
Intel OTC

--
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-07-09 13:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  4:36 [RFCv3 0/5] enable migration of driver pages Gioh Kim
2015-07-07  4:36 ` [RFCv3 1/5] fs/anon_inodes: new interface to create new inode Gioh Kim
2015-07-07  4:36 ` [RFCv3 2/5] mm/compaction: enable mobile-page migration Gioh Kim
2015-07-10 13:07   ` Konstantin Khlebnikov
2015-07-13  8:45     ` Gioh Kim
2015-07-10 13:41   ` Konstantin Khlebnikov
2015-07-07  4:36 ` [RFCv3 3/5] mm/balloon: apply mobile page migratable into balloon Gioh Kim
     [not found]   ` <1436243785-24105-4-git-send-email-gioh.kim-Hm3cg6mZ9cc@public.gmane.org>
2015-07-09  8:07     ` Michael S. Tsirkin
2015-07-10  0:21       ` Gioh Kim
2015-07-10 13:29     ` Konstantin Khlebnikov
2015-07-07  4:36 ` [RFCv3 4/5] mm: call generic migration callbacks Gioh Kim
2015-07-07  4:36 ` [RFCv3 5/5] mm: remove direct calling of migration Gioh Kim
2015-07-07 22:37 ` [RFCv3 0/5] enable migration of driver pages Andrew Morton
2015-07-08  0:02   ` Gioh Kim
     [not found]     ` <559C68B3.3010105-Hm3cg6mZ9cc@public.gmane.org>
2015-07-08  0:07       ` Andrew Morton
2015-07-08  0:19         ` Gioh Kim
2015-07-08  0:35           ` Minchan Kim
2015-07-08 22:47           ` Dave Airlie
2015-07-08 23:55             ` Gioh Kim
2015-07-09 13:08               ` Daniel Vetter
2015-07-09 13:33                 ` Ville Syrjälä [this message]
2015-07-09 14:02                   ` Kirill A. Shutemov
2015-07-10  0:02                 ` Gioh Kim
     [not found] ` <1436243785-24105-1-git-send-email-gioh.kim-Hm3cg6mZ9cc@public.gmane.org>
2015-07-09  1:00   ` Rafael Aquini

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=20150709133301.GG5176@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aquini@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gioh.kim@lge.com \
    --cc=gunho.lee@lge.com \
    --cc=gurugio@hanmail.net \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jlayton@poochiereds.net \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=koct9i@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=list@kvack.org \
    --cc=minchan@kernel.org \
    --cc=mst@redhat.com \
    --cc=open@kvack.org \
    --cc=vbabka@suse.cz \
    --cc=viro@zeniv.linux.org.uk \
    --cc=virtualization@lists.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).