All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/6] Add more vmalloc fallbacks to memory allocations
Date: Mon, 11 Apr 2016 19:31:27 +0200	[thread overview]
Message-ID: <cover.1460394967.git.dsterba@suse.com> (raw)

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 majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-

             reply	other threads:[~2016-04-11 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 17:31 David Sterba [this message]
2016-04-11 17:31 ` [PATCH 1/6] btrfs: send: use vmalloc only as fallback for send_buf David Sterba
2016-04-11 17:31 ` [PATCH 2/6] btrfs: send: use vmalloc only as fallback for read_buf David Sterba
2016-04-11 17:31 ` [PATCH 3/6] btrfs: send: use temporary variable to store allocation size David Sterba
2016-04-11 17:31 ` [PATCH 4/6] btrfs: send: use vmalloc only as fallback for clone_roots David Sterba
2016-04-11 17:31 ` [PATCH 5/6] btrfs: send: use vmalloc only as fallback for clone_sources_tmp David Sterba
2016-04-11 17:31 ` [PATCH 6/6] btrfs: clone: use vmalloc only as fallback for nodesize bufer David Sterba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1460394967.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.