using non contiguous memory in nfs_idmap_new()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear linux-nfs,

I have a box that has recently been victim of an OOM caused by
nfs_idmap_new() attempting to allocate a large amount of contiguous
memory. This problem has been reported previously here [0] and I
understand the real fix is to use CONFIG_NFS_USE_NEW_IDMAPPER. However
I was wondering whether using non contiguous memory instead would be a
valid workaround, especially considering the new ID mapper is not
enabled by default. I have actually written a patch to that effect as
I don't see any specific reason why that struct would need to be in
contiguous memory.

So before I do anything stupid with that patch,
a) is there any good reason to use kzalloc() instead of vzalloc() in
nfs_idmap_new()?
b) would you consider a patch that would make the function use vzalloc()?

Thanks,
Adrien Kunysz

[0] http://www.spinics.net/lists/linux-nfs/msg22248.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux