From: Mel Gorman <mgorman@techsingularity.net>
To: Gioh Kim <gioh.kim@lge.com>,
jlayton@poochiereds.net, bfields@fieldses.org, vbabka@suse.cz,
iamjoonsoo.kim@lge.com, viro@zeniv.linux.org.uk, mst@redhat.com,
koct9i@gmail.com, minchan@kernel.org, aquini@redhat.com,
linux-fsdevel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-mm@kvack.org, dri-devel@lists.freedesktop.org,
akpm@linux-foundation.org, Gioh Kim <gurugio@hanmail.net>
Subject: Re: [PATCH 0/4] enable migration of driver pages
Date: Wed, 29 Jul 2015 13:16:14 +0100 [thread overview]
Message-ID: <20150729121614.GA19352@techsingularity.net> (raw)
In-Reply-To: <20150729105554.GU16722@phenom.ffwll.local>
On Wed, Jul 29, 2015 at 12:55:54PM +0200, Daniel Vetter wrote:
> On Wed, Jul 29, 2015 at 11:49:45AM +0100, Mel Gorman wrote:
> > On Mon, Jul 13, 2015 at 05:35:15PM +0900, Gioh Kim wrote:
> > > My ARM-based platform occured severe fragmentation problem after long-term
> > > (several days) test. Sometimes even order-3 page allocation failed. It has
> > > memory size 512MB ~ 1024MB. 30% ~ 40% memory is consumed for graphic processing
> > > and 20~30 memory is reserved for zram.
> > >
> >
> > The primary motivation of this series is to reduce fragmentation by allowing
> > more kernel pages to be moved. Conceptually that is a worthwhile goal but
> > there should be at least one major in-kernel user and while balloon
> > pages were a good starting point, I think we really need to see what the
> > zram changes look like at the same time.
>
> I think gpu drivers really would be the perfect candidate for compacting
> kernel page allocations. And this also seems the primary motivation for
> this patch series, so I think that's really what we should use to judge
> these patches.
>
> Of course then there's the seemingly eternal chicken/egg problem of
> upstream gpu drivers for SoCs :(
I recognised that the driver he had modified was not an in-tree user so
it did not really help the review or the design. I did not think it was
very fair to ask that an in-tree GPU driver be converted when it would not
help the embedded platform of interest. Converting zram is both a useful
illustration of the aops requirements and is expected to be beneficial on
the embedded platform. Now, if a GPU driver author was willing to convert
theirs as an example then that would be useful!
--
Mel Gorman
SUSE Labs
--
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:[~2015-07-29 12:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 8:35 [PATCH 0/4] enable migration of driver pages Gioh Kim
2015-07-13 8:35 ` [PATCH 1/4] fs/anon_inodes: new interface to create new inode Gioh Kim
2015-07-29 10:50 ` Mel Gorman
2015-07-13 8:35 ` [PATCH 2/4] mm/compaction: enable mobile-page migration Gioh Kim
2015-07-27 13:55 ` Vlastimil Babka
2015-07-27 18:56 ` Konstantin Khlebnikov
2015-07-28 0:21 ` Gioh Kim
2015-07-29 10:52 ` Mel Gorman
2015-07-31 10:43 ` Minchan Kim
2015-08-10 7:19 ` Minchan Kim
2015-07-13 8:35 ` [PATCH 3/4] mm/balloon: apply mobile page migratable into balloon Gioh Kim
2015-07-13 8:35 ` [PATCH 4/4] mm: remove direct calling of migration Gioh Kim
2015-07-27 13:58 ` Vlastimil Babka
2015-07-28 0:26 ` Gioh Kim
2015-07-13 9:24 ` [PATCH 0/4] enable migration of driver pages Konstantin Khlebnikov
2015-07-13 10:02 ` Gioh Kim
2015-07-13 14:20 ` Rafael Aquini
2015-07-29 10:49 ` Mel Gorman
2015-07-29 10:55 ` Daniel Vetter
2015-07-29 12:16 ` Mel Gorman [this message]
2015-07-29 12:46 ` Daniel Vetter
2015-07-30 0:21 ` Gioh Kim
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=20150729121614.GA19352@techsingularity.net \
--to=mgorman@techsingularity.net \
--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=gurugio@hanmail.net \
--cc=iamjoonsoo.kim@lge.com \
--cc=jlayton@poochiereds.net \
--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=minchan@kernel.org \
--cc=mst@redhat.com \
--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).