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:   Fri, 21 Jan 2022 11:24:32 +0800
From:   Tony Lu <tonylu@...ux.alibaba.com>
To:     Karsten Graul <kgraul@...ux.ibm.com>
Cc:     kuba@...nel.org, davem@...emloft.net, netdev@...r.kernel.org,
        linux-s390@...r.kernel.org
Subject: Re: [PATCH net-next] net/smc: Use kvzalloc for allocating
 smc_link_group

On Thu, Jan 20, 2022 at 03:50:26PM +0100, Karsten Graul wrote:
> On 20/01/2022 15:09, Tony Lu wrote:
> > When analyzed memory usage of SMC, we found that the size of struct
> > smc_link_group is 16048 bytes, which is too big for a busy machine to
> > allocate contiguous memory. Using kvzalloc instead that falls back to
> > vmalloc if there has not enough contiguous memory.
> 
> I am wondering where the needed contiguous memory for the required RMB buffers should come from when 
> you don't even get enough storage for the initial link group?

Yes, this is what I want to talking about. The RMB buffers size inherits
from TCP, we cannot assume that RMB is always larger than 16k bytes, the
tcp_mem can be changed on the fly, and it can be tuned to very small for
saving memory. Also, If we freed existed link group or somewhere else,
we can allocate enough contiguous memory for the new link group.

> The idea is that when the system is so low on contiguous memory then a link group creation should fail 
> early, because most of the later buffer allocations will also fail then later.

IMHO, it is not a "pre-checker" for allocating buffer, it is a reminder
for us to save contiguous memory, this is a precious resource, and a
possible way to do this. This patch is not the best approach to solve
this problem, but the simplest one. A possible approach to allocate
link array in link group with a pointer to another memory. Glad to hear
your advice.

Thanks,
Tony Lu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ