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
| ||
|
Date: Thu, 22 Mar 2018 19:06:06 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: Baoquan He <bhe@...hat.com> Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org, takahiro.akashi@...aro.org, ebiederm@...ssion.com, vgoyal@...hat.com, dyoung@...hat.com, prudo@...ux.vnet.ibm.com Subject: Re: [PATCH 1/2] resource: add walk_system_ram_res_rev() On Fri, 23 Mar 2018 08:58:45 +0800 Baoquan He <bhe@...hat.com> wrote: > > erk, this is pretty nasty. Isn't there a better way :( > > Yes, this is not efficient. > > In struct resource{}, ->sibling list is a singly linked list. I ever > thought about changing it to doubly linked list, yet not very sure if > it will have effect since struct resource is a core data structure. Switching to a list_head sounds OK. The only issue really is memory consumption and surely we don't have tens of thousands of struct resources floating about(?). Or if we do have a lot, the machine is presumably huge (hope?). > AKASHI's method is more acceptable, and currently only kexec has this > requirement. What method is that?
Powered by blists - more mailing lists