From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Kyungmin Park <kmpark@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
minchan@kernel.org
Subject: Re: [PATCH] mm: cma: fix accounting of CMA pages placed in high memory
Date: Tue, 05 Feb 2013 09:56:21 +0100 [thread overview]
Message-ID: <5110C935.6020308@samsung.com> (raw)
In-Reply-To: <20130205082822.GE21389@suse.de>
Hello,
On 2/5/2013 9:28 AM, Mel Gorman wrote:
> On Tue, Feb 05, 2013 at 08:29:26AM +0900, Kyungmin Park wrote:
> > >
> > > (This information is needed so that others can make patch-scheduling
> > > decisions and should be included in all bugfix changelogs unless it is
> > > obvious).
> >
> > CMA Highmem support is new feature. so don't need to go stable tree.
> >
>
> You could have given a lot more information to that question!
>
> How new a feature is it?
ARM DMA-mapping, the only in-kernel client of CMA, will gain himem
support in
v3.9. On the other hand, there might be out of tree clients of
alloc_contig_migrate_range()/dma_alloc_from_contiguous() API. If you think
we should care about them, then this patch might need to be backported
to stable kernels.
> Does this mean that this patch must go in before
> 3.8 releases or is it a fix against a patch that is only in Andrew's tree?
> If the patch is only in Andrew's tree, which one is it and should this be
> folded in as a fix?
>
> On a semi-related note; is there a plan for backporting highmem support for
> the LTSI kernel considering it's aimed at embedded and CMA was highlighted
> in their announcment for 3.4 support?
I've just noticed recently that LTSI released v3.4 kernel with CMA support.
I've checked that code only briefly and noticed that it didn't have all the
CMA related patches which are available in v3.8-rc1. I will take a look at
that code and maybe I will find some time to backport some more patches from
mainline, but please note that mainline kernel has higher priority.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
--
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:[~2013-02-05 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 10:27 Marek Szyprowski
2013-02-04 12:55 ` Kyungmin Park
2013-02-04 23:06 ` Andrew Morton
2013-02-04 23:29 ` Kyungmin Park
2013-02-04 23:43 ` Minchan Kim
2013-02-04 23:52 ` Kyungmin Park
2013-02-05 0:40 ` Minchan Kim
2013-02-05 8:38 ` Marek Szyprowski
2013-02-05 8:47 ` Minchan Kim
2013-02-05 8:28 ` Mel Gorman
2013-02-05 8:56 ` Marek Szyprowski [this message]
2013-02-04 23:34 ` Minchan Kim
2013-02-05 7:10 ` Marek Szyprowski
2013-02-05 7:34 ` Minchan Kim
2013-02-19 13:27 ` Simon Jeons
2013-02-20 2:57 ` Kyungmin Park
2013-02-20 5:31 ` Simon Jeons
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=5110C935.6020308@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=kmpark@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--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