lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20171226180622.GA31719@mobilestation> Date: Tue, 26 Dec 2017 21:06:22 +0300 From: Serge Semin <fancer.lancer@...il.com> To: Marcin Nowakowski <marcin.nowakowski@...s.com> Cc: ralf@...ux-mips.org, paul.burton@...tec.com, rabinv@...s.com, matt.redfearn@...tec.com, james.hogan@...tec.com, alexander.sverdlin@...ia.com, marcin.nowakowski@...tec.com, f.fainelli@...il.com, kumba@...too.org, Sergey.Semin@...latforms.ru, linux-mips@...ux-mips.org, linux-kernel@...r.kernel.org Subject: Re: [RFC] MIPS memblock: Remove bootmem code and switch to NO_BOOTMEM On Fri, Dec 22, 2017 at 08:18:09AM +0100, Marcin Nowakowski <marcin.nowakowski@...s.com> wrote: > 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@...tec.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. > Hello Marcin, Thanks for the willing to help. I'll CC the patchset to you when it's ready. -Sergey > Marcin
Powered by blists - more mailing lists