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]
Date:   Tue, 15 Oct 2019 12:00:25 +0800
From:   Tiezhu Yang <yangtiezhu@...ngson.cn>
To:     Huacai Chen <chenhc@...ote.com>
Cc:     Paul Burton <paul.burton@...s.com>,
        Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <jhogan@...nel.org>,
        "open list:MIPS" <linux-mips@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MIPS: Loongson: Make default kernel log buffer size as
 128KB for Loongson3

On 10/15/2019 11:36 AM, Huacai Chen wrote:
> On Tue, Oct 15, 2019 at 10:12 AM Tiezhu Yang <yangtiezhu@...ngson.cn> wrote:
>> When I update kernel with loongson3_defconfig based on the Loongson 3A3000
>> platform, then using dmesg command to show kernel ring buffer, the initial
>> kernel messages have disappeared due to the log buffer is too small, it is
>> better to change the default kernel log buffer size from 16KB to 128KB.
>>
>> Signed-off-by: Tiezhu Yang <yangtiezhu@...ngson.cn>
>> ---
>>   arch/mips/configs/loongson3_defconfig | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/mips/configs/loongson3_defconfig b/arch/mips/configs/loongson3_defconfig
>> index 90ee008..3aa2201 100644
>> --- a/arch/mips/configs/loongson3_defconfig
>> +++ b/arch/mips/configs/loongson3_defconfig
>> @@ -12,7 +12,7 @@ CONFIG_TASKSTATS=y
>>   CONFIG_TASK_DELAY_ACCT=y
>>   CONFIG_TASK_XACCT=y
>>   CONFIG_TASK_IO_ACCOUNTING=y
>> -CONFIG_LOG_BUF_SHIFT=14
>> +CONFIG_LOG_BUF_SHIFT=17
> Hi, Tiezhu,
>
> Why you choose 128KB but not 64KB or 256KB? I found 64KB is enough for
> our cases. And if you really need more, I think 256KB could be better
> because there are many platforms choose 256KB.

Hi Huacai,

Thanks for your reply and suggestion, I will send a v2 patch.

Thanks,

Tiezhu Yang

>
> Huacai
>
>>   CONFIG_MEMCG=y
>>   CONFIG_MEMCG_SWAP=y
>>   CONFIG_BLK_CGROUP=y
>> --
>> 2.1.0
>>
>>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ