From: Andrew Morton <akpm@linux-foundation.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-mm@kvack.org, m.szyprowski@samsung.com, mina86@mina86.com,
minchan@kernel.org, mgorman@suse.de, hughd@google.com,
kyungmin.park@samsung.com
Subject: Re: [PATCH v4 4/4] cma: fix watermark checking
Date: Mon, 24 Sep 2012 14:30:12 -0700 [thread overview]
Message-ID: <20120924143012.f72ad2bc.akpm@linux-foundation.org> (raw)
In-Reply-To: <201209241130.43480.b.zolnierkie@samsung.com>
On Mon, 24 Sep 2012 11:30:43 +0200
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> wrote:
> On Wednesday 19 September 2012 21:51:02 Andrew Morton wrote:
> > >
> > > /*
> > > * Check whether it is worth even starting compaction. The order check is
> > > @@ -879,6 +880,10 @@ unsigned long try_to_compact_pages(struct zonelist *zonelist,
> > >
> > > count_vm_event(COMPACTSTALL);
> > >
> > > +#ifdef CONFIG_CMA
> > > + if (allocflags_to_migratetype(gfp_mask) == MIGRATE_MOVABLE)
> > > + alloc_flags |= ALLOC_CMA;
> >
> > I find this rather obscure. What is the significance of
> > MIGRATE_MOVABLE here? If it had been
> >
> > : if (allocflags_to_migratetype(gfp_mask) == MIGRATE_CMA)
> > : alloc_flags |= ALLOC_CMA;
> >
> > then I'd have read straight past it. But it's unclear what's happening
> > here. If we didn't have to resort to telepathy to understand the
> > meaning of ALLOC_CMA, this wouldn't be so hard.
This?
Or am I being more than usually thick? Is everyone else finding
if (allocflags_to_migratetype(gfp_mask) == MIGRATE_MOVABLE)
alloc_flags |= ALLOC_CMA;
to be blindingly obvious?
--
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>
prev parent reply other threads:[~2012-09-24 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 14:29 [PATCH v4 0/4] cma: fix watermark checking Bartlomiej Zolnierkiewicz
2012-09-14 14:29 ` [PATCH v4 1/4] mm: fix tracing in free_pcppages_bulk() Bartlomiej Zolnierkiewicz
2012-09-19 7:07 ` Yasuaki Ishimatsu
2012-09-19 7:32 ` Minchan Kim
2012-09-19 7:45 ` Yasuaki Ishimatsu
2012-09-19 8:03 ` Minchan Kim
2012-09-19 18:07 ` KOSAKI Motohiro
2012-09-19 19:28 ` Andrew Morton
2012-09-14 14:29 ` [PATCH v4 2/4] cma: fix counting of isolated pages Bartlomiej Zolnierkiewicz
2012-09-14 14:29 ` [PATCH v4 3/4] cma: count free CMA pages Bartlomiej Zolnierkiewicz
2012-09-14 14:29 ` [PATCH v4 4/4] cma: fix watermark checking Bartlomiej Zolnierkiewicz
2012-09-19 19:51 ` Andrew Morton
2012-09-24 9:30 ` Bartlomiej Zolnierkiewicz
2012-09-24 21:30 ` Andrew Morton [this message]
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=20120924143012.f72ad2bc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=b.zolnierkie@samsung.com \
--cc=hughd@google.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mgorman@suse.de \
--cc=mina86@mina86.com \
--cc=minchan@kernel.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).