All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.cz>
Subject: [PATCH 0/6] Btrfs send updates - reduce memory consumption
Date: Mon,  3 Feb 2014 19:21:46 +0100	[thread overview]
Message-ID: <cover.1391447200.git.dsterba@suse.cz> (raw)

[Sorry if you see this twice, first attempt hasn't appeared in the list yet]

This reduces size of the path buffer in common case. Has been tested by
xfstests, but at the moment v3.13 with or without this patch blows, so I'm
sending it anyway.

Based on current btrfs-next/master.

David Sterba (6):
  btrfs: send: remove prepared member from fs_path
  btrfs: send: remove virtual_mem member from fs_path
  btrfs: send: squeeze bitfilelds in fs_path
  btrfs: send: lower memory requirements in common case
  btrfs: send: remove BUG from process_all_refs
  btrfs: send: remove BUG_ON from name_cache_delete

 fs/btrfs/send.c |  153 ++++++++++++++++++++++--------------------------------
 1 files changed, 62 insertions(+), 91 deletions(-)

-- 
1.7.9


             reply	other threads:[~2014-02-03 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-03 18:21 David Sterba [this message]
2014-02-03 18:23 ` [PATCH 1/6] btrfs: send: remove prepared member from fs_path David Sterba
2014-02-03 18:23 ` [PATCH 2/6] btrfs: send: remove virtual_mem " David Sterba
2014-02-03 18:23 ` [PATCH 3/6] btrfs: send: squeeze bitfilelds in fs_path David Sterba
2014-02-03 18:23 ` [PATCH 4/6] btrfs: send: lower memory requirements in common case David Sterba
2014-02-03 18:24 ` [PATCH 5/6] btrfs: send: remove BUG from process_all_refs David Sterba
2014-02-03 18:24 ` [PATCH 6/6] btrfs: send: remove BUG_ON from name_cache_delete 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.1391447200.git.dsterba@suse.cz \
    --to=dsterba@suse.cz \
    --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.