Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751764AbdLVH0v (ORCPT ); Fri, 22 Dec 2017 02:26:51 -0500 Received: from 9pmail.ess.barracuda.com ([64.235.150.225]:41957 "EHLO 9pmail.ess.barracuda.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750786AbdLVH0o (ORCPT ); Fri, 22 Dec 2017 02:26:44 -0500 X-Greylist: delayed 502 seconds by postgrey-1.27 at vger.kernel.org; Fri, 22 Dec 2017 02:26:44 EST Subject: Re: [RFC] MIPS memblock: Remove bootmem code and switch to NO_BOOTMEM To: Serge Semin , , , , , , , , , CC: , , References: <20171219201400.GA10185@mobilestation> From: Marcin Nowakowski Message-ID: Date: Fri, 22 Dec 2017 08:18:09 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171219201400.GA10185@mobilestation> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [192.168.159.66] X-BESS-ID: 1513927601-298552-20475-41276-9 X-BESS-VER: 2017.16-r1712182224 X-BESS-Apparent-Source-IP: 12.201.5.28 X-BESS-Outbound-Spam-Score: 0.00 X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.188251 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------- 0.00 BSF_BESS_OUTBOUND META: BESS Outbound 0.00 BSF_SC0_MISMATCH_TO META: Envelope rcpt doesn't match header X-BESS-Outbound-Spam-Status: SCORE=0.00 using account:ESS59374 scores of KILL_LEVEL=7.0 tests=BSF_BESS_OUTBOUND, BSF_SC0_MISMATCH_TO X-BESS-BRTS-Status: 1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1100 Lines: 23 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