From: Marcin Nowakowski <marcin.nowakowski@mips.com>
To: Serge Semin <fancer.lancer@gmail.com>, <ralf@linux-mips.org>,
<paul.burton@imgtec.com>, <rabinv@axis.com>,
<matt.redfearn@imgtec.com>, <james.hogan@imgtec.com>,
<alexander.sverdlin@nokia.com>, <marcin.nowakowski@imgtec.com>,
<f.fainelli@gmail.com>, <kumba@gentoo.org>
Cc: <Sergey.Semin@t-platforms.ru>, <linux-mips@linux-mips.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC] MIPS memblock: Remove bootmem code and switch to NO_BOOTMEM
Date: Fri, 22 Dec 2017 08:18:09 +0100 [thread overview]
Message-ID: <eace1075-4e3f-1f0c-50ed-73a566ecd39b@mips.com> (raw)
In-Reply-To: <20171219201400.GA10185@mobilestation>
Hi Serge,
On 19.12.2017 21:14, Serge Semin wrote:
> Hello folks,
>
> Almost a year ago I sent a patchset to the Linux MIPS community. The main target of the patchset
> was to get rid from the old bootmem allocator usage at the MIPS architecture. Additionally I had
> a problem with CMA usage on my MIPS machine due to some struct page-related issue. Moving to the
> memblock allocator fixed the problem and gave us benefits like smaller memory consumption,
> powerful memblock API to be used within the arch code.
>
> @marcin.nowakowski@imgtec.com. Could you confirm if you are still interested in the patchset and
> ready to update the Loongson64 platform code so one would be compatible with it?
I am currently working on different projects, but I will try to do my
best to help with this (but just might require more time than I would
otherwise need).
Given the scale of the task and the amount of testing required, I expect
that it will take a while to get a complete set of patches reviewed and
tested which should hopefully be enough to fix support for all platforms
affected.
Marcin
next prev parent reply other threads:[~2017-12-22 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 20:14 [RFC] MIPS memblock: Remove bootmem code and switch to NO_BOOTMEM Serge Semin
2017-12-20 8:20 ` Alexander Sverdlin
[not found] ` <65E0D1C69B83F54F8D5C962B651A2DEC026B902C@MIPSMAIL01.mipstec.com>
[not found] ` <a3865a42-d0cf-f48d-3bda-e3cd85f5b49b@mips.com>
2017-12-21 18:21 ` Serge Semin
2017-12-22 7:18 ` Marcin Nowakowski [this message]
2017-12-26 18:06 ` Serge Semin
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=eace1075-4e3f-1f0c-50ed-73a566ecd39b@mips.com \
--to=marcin.nowakowski@mips.com \
--cc=Sergey.Semin@t-platforms.ru \
--cc=alexander.sverdlin@nokia.com \
--cc=f.fainelli@gmail.com \
--cc=fancer.lancer@gmail.com \
--cc=james.hogan@imgtec.com \
--cc=kumba@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=marcin.nowakowski@imgtec.com \
--cc=matt.redfearn@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=rabinv@axis.com \
--cc=ralf@linux-mips.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