Displaying 3 results from an estimated 3 matches for "slab_out_of_memori".
Did you mean:
slab_out_of_memory
2017 May 22
4
[PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions
On Mon, May 22, 2017 at 12:50:39PM +0200, SF Markus Elfring wrote:
> > Why are you trying to get rid of memory allocation failure messages?
>
> Do you find information from a Linux allocation failure report sufficient
> for any function implementations here?
If kmalloc() and friends guarantee to print a warning and backtrace on
every allocation failure, then there's no need
2017 May 22
4
[PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions
On Mon, May 22, 2017 at 12:50:39PM +0200, SF Markus Elfring wrote:
> > Why are you trying to get rid of memory allocation failure messages?
>
> Do you find information from a Linux allocation failure report sufficient
> for any function implementations here?
If kmalloc() and friends guarantee to print a warning and backtrace on
every allocation failure, then there's no need
2017 May 22
0
[PATCH 2/2] vhost/scsi: Delete error messages for failed memory allocations in five functions
On Mon, May 22, 2017 at 12:23:20PM +0100, Stefan Hajnoczi wrote:
> I'm not sure if kmalloc() and friends guarantee to show
> a message (not just the first time, but for every failed allocation)?
>
It prints multiple times, but it's ratelimited. It can also be disabled
using a config option.
See slab_out_of_memory().
regards,
dan carpenter