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>] [day] [month] [year] [list]
Message-ID: <CAAvDm6YDCoqib3oaof03K-JwGNd5t2krc9-L3moZ_cfuQOuQsw@mail.gmail.com>
Date:   Fri, 26 Jun 2020 20:40:47 +0800
From:   孙世龙 sunshilong <sunshilong369@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Are there some potential problems that I should be aware of if I
 allocate the memory which doesn't have any relation to peripheral
 hardwares(i.e. DMA,PCI,serial port and etc) by vmalloc() instead of kmalloc()?

Hi, list

Besides kmalloc() is more efficient, are there some potential problems
that I should be aware of if I allocate the memory which doesn't have
any relation to peripheral hardwares(i.e. DMA,PCI,serial port and etc)
by vmalloc() instead of kmalloc() to avoid the page allocation failure
caused by kmalloc() while there are too many memory fragments?

Thank you for your attention to this matter.
Best Regards.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ