Hi,
inspired by a recent fix where we tried to kmalloc a 64k nodesize buffer,
without the vmalloc fallback, and failed. This series add the "kmalloc-first
and vmalloc-fallback" logic to more places, namely to the buffers used during
send. If the memory is not fragmented, kmalloc succeeds and does not take the
resources required for the mappings.
----------------------------------------------------------------
The following changes since commit 56f23fdbb600e6087db7b009775b95ce07cc3195:
Btrfs: fix file/data loss caused by fsync after rename and new inode
(2016-04-06 17:01:44 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git dev/kvalloc
for you to fetch changes up to c3e3930516c4d14ed1d6d70964fbc4f3faa36844:
btrfs: clone: use vmalloc only as fallback for nodesize bufer (2016-04-11
19:06:39 +0200)
----------------------------------------------------------------
David Sterba (6):
btrfs: send: use vmalloc only as fallback for send_buf
btrfs: send: use vmalloc only as fallback for read_buf
btrfs: send: use temporary variable to store allocation size
btrfs: send: use vmalloc only as fallback for clone_roots
btrfs: send: use vmalloc only as fallback for clone_sources_tmp
btrfs: clone: use vmalloc only as fallback for nodesize bufer
fs/btrfs/ioctl.c | 13 ++++++++-----
fs/btrfs/send.c | 56 +++++++++++++++++++++++++++++++++++---------------------
2 files changed, 43 insertions(+), 26 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
