From: Anand Jain <anand.jain@oracle.com>
To: Christoph Hellwig <hch@lst.de>, David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org, Liu Bo <bo.li.liu@oracle.com>
Subject: Re: [PATCH 1/8] btrfs: bioset allocations will never fail, adapt our helpers
Date: Wed, 7 Jun 2017 14:52:36 +0800 [thread overview]
Message-ID: <377590f2-ff26-3fc3-7c38-d91d44b503db@oracle.com> (raw)
In-Reply-To: <20170606104431.GA24297@lst.de>
> #define __GFP_RECLAIM ((__force gfp_t)(___GFP_DIRECT_RECLAIM|___GFP_KSWAPD_RECLAIM))
>
>
> #define GFP_NOFS (__GFP_RECLAIM | __GFP_IO)
Ah. Thanks.
next prev parent reply other threads:[~2017-06-07 6:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 16:58 [PATCH 0/8] Bio allocation and error handling cleanups David Sterba
2017-06-02 16:58 ` [PATCH 1/8] btrfs: bioset allocations will never fail, adapt our helpers David Sterba
2017-06-03 5:10 ` Christoph Hellwig
2017-06-06 10:21 ` Anand Jain
2017-06-06 10:44 ` Christoph Hellwig
2017-06-07 6:52 ` Anand Jain [this message]
2017-06-06 10:51 ` David Sterba
2017-06-07 9:10 ` Anand Jain
2017-06-02 16:58 ` [PATCH 2/8] btrfs: btrfs_bio_alloc never fails, skip error handling David Sterba
2017-06-07 9:11 ` Anand Jain
2017-06-02 16:58 ` [PATCH 3/8] btrfs: btrfs_bio_clone " David Sterba
2017-06-07 9:11 ` Anand Jain
2017-06-07 18:19 ` Omar Sandoval
2017-06-12 13:13 ` David Sterba
2017-06-02 16:58 ` [PATCH 4/8] btrfs: btrfs_io_bio_alloc " David Sterba
2017-06-07 9:11 ` Anand Jain
2017-06-02 16:58 ` [PATCH 5/8] btrfs: sink gfp parameter to btrfs_bio_clone David Sterba
2017-06-07 9:12 ` Anand Jain
2017-06-02 16:58 ` [PATCH 6/8] btrfs: remove redundant parameters from btrfs_bio_alloc David Sterba
2017-06-07 7:40 ` Anand Jain
2017-06-12 13:09 ` David Sterba
2017-06-02 16:58 ` [PATCH 7/8] btrfs: opencode trivial compressed_bio_alloc, simplify error handling David Sterba
2017-06-07 9:21 ` Anand Jain
2017-06-02 16:58 ` [PATCH 8/8] btrfs: pass bytes to btrfs_bio_alloc David Sterba
2017-06-07 9:22 ` Anand Jain
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=377590f2-ff26-3fc3-7c38-d91d44b503db@oracle.com \
--to=anand.jain@oracle.com \
--cc=bo.li.liu@oracle.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--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.