linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Mel Gorman <mgorman@techsingularity.net>,
	linux-mm@kvack.org, kernel@pengutronix.de,
	patchwork-lst@pengutronix.de
Subject: Re: [PATCH] mm: alloc_contig: re-allow CMA to compact FS pages
Date: Fri, 13 Jan 2017 14:35:10 +0100	[thread overview]
Message-ID: <1484314510.30810.31.camel@pengutronix.de> (raw)
In-Reply-To: <b7c0b216-5777-ecb3-589a-24288c2eeec8@suse.cz>

Am Freitag, den 13.01.2017, 14:24 +0100 schrieb Vlastimil Babka:
> On 01/13/2017 12:51 PM, Lucas Stach wrote:
> > Commit 73e64c51afc5 (mm, compaction: allow compaction for GFP_NOFS requests)
> > changed compation to skip FS pages if not explicitly allowed to touch them,
> > but missed to update the CMA compact_control.
> >
> > This leads to a very high isolation failure rate, crippling performance of
> > CMA even on a lightly loaded system. Re-allow CMA to compact FS pages by
> > setting the correct GFP flags, restoring CMA behavior and performance to
> > the kernel 4.9 level.
> >
> > Fixes: 73e64c51afc5 (mm, compaction: allow compaction for GFP_NOFS requests)
> > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> 
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> 
> It's true that this restores the behavior for CMA to 4.9. But it also reveals 
> that CMA always implicitly assumed to be called from non-fs context. That's 
> expectable for the original CMA use-case of drivers for devices such as cameras, 
> but I now wonder if there's danger when CMA gets invoked via dma-cma layer with 
> generic cma range for e.g. a disk device... I guess that would be another 
> argument for scoped GFP_NOFS, which should then be applied to adjust the 
> gfp_mask here. Or we could apply at least memalloc_noio_flags() right now, which 
> should already handle the disk device -> dma -> cma scenario?

That's right. But I don't think we need to fix this for 4.10. The
minimal fix in this patch brings things back to the old assumptions.

As dma allocations already carry proper GFP flags it's just a matter of
passing them through to CMA, to make things work correctly. I'll cook up
a follow up patch for that, but I think this should wait for the next
merge window to be applied.

Regards,
Lucas

--
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:[~2017-01-13 13:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 11:51 Lucas Stach
2017-01-13 12:19 ` Michal Hocko
2017-01-13 13:24 ` Vlastimil Babka
2017-01-13 13:35   ` Lucas Stach [this message]
2017-01-13 13:47     ` Michal Hocko

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=1484314510.30810.31.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=patchwork-lst@pengutronix.de \
    --cc=vbabka@suse.cz \
    /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