From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, clm@fb.com
Subject: [PATCH 0/3] GFP flags adjustments, part 2
Date: Tue, 19 Jan 2016 11:37:00 +0100 [thread overview]
Message-ID: <cover.1453199502.git.dsterba@suse.com> (raw)
Hi,
a few more tweaks to the GFP flags, for 4.5. This is low-risk and still preparatory so
we can narrow down the contexts where we can utilize the more fine-grained GFP flags and
attack the memory allocation failures.
----------------------------------------------------------------
The following changes since commit 39a27ec1004e886f1d949bdb8f2616896d02c5c2:
btrfs: use GFP_KERNEL for xattr and acl allocations (2015-12-03 15:03:44 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git dev/gfp-flags
for you to fetch changes up to 3677d94d23ae74d584ba61396aa51e82bb53e2d4:
btrfs: scrub: use GFP_KERNEL on the submission path (2016-01-19 10:17:31 +0100)
----------------------------------------------------------------
David Sterba (3):
btrfs: send: use GFP_KERNEL everywhere
btrfs: reada: use GFP_KERNEL everywhere
btrfs: scrub: use GFP_KERNEL on the submission path
fs/btrfs/reada.c | 10 +++++-----
fs/btrfs/scrub.c | 24 +++++++++++++-----------
fs/btrfs/send.c | 36 ++++++++++++++++++------------------
3 files changed, 36 insertions(+), 34 deletions(-)
--
2.6.3
next reply other threads:[~2016-01-19 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 10:37 David Sterba [this message]
2016-01-19 10:37 ` [PATCH 1/3] btrfs: send: use GFP_KERNEL everywhere David Sterba
2016-01-19 10:37 ` [PATCH 2/3] btrfs: reada: " David Sterba
2016-01-19 10:37 ` [PATCH 3/3] btrfs: scrub: use GFP_KERNEL on the submission path 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.1453199502.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@fb.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.