From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/5] GFP flags and allocation cleanups
Date: Fri, 14 Jul 2017 19:35:15 +0200 [thread overview]
Message-ID: <cover.1500053599.git.dsterba@suse.com> (raw)
A few more NOFS -> KERNEL conversions and simplification of memory allocations.
David Sterba (5):
btrfs: use GFP_KERNEL in mount and remount
btrfs: use GFP_KERNEL in btrfs_defrag_file
btrfs: defrag: make readahead state allocation failure non-fatal
btrfs: factor reading progress out of btrfs_dev_replace_status
btrfs: simplify btrfs_dev_replace_kthread
fs/btrfs/dev-replace.c | 74 ++++++++++++++++++++++++++++----------------------
fs/btrfs/ioctl.c | 20 +++++++-------
fs/btrfs/super.c | 15 +++++-----
3 files changed, 59 insertions(+), 50 deletions(-)
--
2.13.0
next reply other threads:[~2017-07-14 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 17:35 David Sterba [this message]
2017-07-14 17:35 ` [PATCH 1/5] btrfs: use GFP_KERNEL in mount and remount David Sterba
2017-07-14 17:35 ` [PATCH 2/5] btrfs: use GFP_KERNEL in btrfs_defrag_file David Sterba
2017-07-14 17:35 ` [PATCH 3/5] btrfs: defrag: make readahead state allocation failure non-fatal David Sterba
2017-07-14 17:35 ` [PATCH 4/5] btrfs: factor reading progress out of btrfs_dev_replace_status David Sterba
2017-07-14 17:35 ` [PATCH 5/5] btrfs: simplify btrfs_dev_replace_kthread 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.1500053599.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).