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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eace1075-4e3f-1f0c-50ed-73a566ecd39b@mips.com>
Date:   Fri, 22 Dec 2017 08:18:09 +0100
From:   Marcin Nowakowski <marcin.nowakowski@...s.com>
To:     Serge Semin <fancer.lancer@...il.com>, <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>
CC:     <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

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.

Marcin

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ