From: Jens Axboe <axboe@kernel.dk>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Goldwyn Rodrigues <rgoldwyn@suse.de>,
hch@lst.de, jack@suse.cz, akpm@linux-foundation.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH 0/10 v13] merge request: No wait AIO
Date: Mon, 19 Jun 2017 17:36:05 -0600 [thread overview]
Message-ID: <1de9d545-8811-4dfa-22db-f5172f122a95@kernel.dk> (raw)
In-Reply-To: <20170619233439.GL10672@ZenIV.linux.org.uk>
On 06/19/2017 05:34 PM, Al Viro wrote:
> On Mon, Jun 19, 2017 at 05:15:16PM -0600, Jens Axboe wrote:
>> On 06/19/2017 10:33 AM, Goldwyn Rodrigues wrote:
>>> Jens,
>>>
>>> As Christoph suggested, I am sending the patches against the block
>>> tree for merge since the block layer changes had the most conflicts.
>>> My tree is at https://github.com/goldwynr/linux/tree/nowait-block
>>
>> I can merge it for 4.13, but I need Al to be happy with it first.
>
> FWIW, it's really a matter of who gets more conflicts - I'm OK with the
> general shape of that code and it could go through either tree (or both,
> for that matter, if an immutable branch is promised).
I'm still hopeful that the write hint patchset will make it as well,
which will definitely conflict with this. So if you don't mind, I'd
like to queue it through the block tree. The block for-4.x/ branches
are not rebased.
--
Jens Axboe
next prev parent reply other threads:[~2017-06-19 23:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:33 [PATCH 0/10 v13] merge request: No wait AIO Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 01/10] fs: Separate out kiocb flags setup based on RWF_* flags Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 02/10] fs: Introduce filemap_range_has_page() Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 03/10] fs: Use RWF_* flags for AIO operations Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 04/10] fs: Introduce RWF_NOWAIT and FMODE_AIO_NOWAIT Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 05/10] fs: return if direct I/O will trigger writeback Goldwyn Rodrigues
2017-06-19 16:44 ` Al Viro
2017-06-19 16:33 ` [PATCH 06/10] fs: Introduce IOMAP_NOWAIT Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 07/10] block: return on congested block device Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 08/10] ext4: nowait aio support Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 09/10] xfs: " Goldwyn Rodrigues
2017-06-19 16:33 ` [PATCH 10/10] btrfs: " Goldwyn Rodrigues
2017-06-19 23:15 ` [PATCH 0/10 v13] merge request: No wait AIO Jens Axboe
2017-06-19 23:20 ` Goldwyn Rodrigues
2017-06-19 23:34 ` Al Viro
2017-06-19 23:36 ` Jens Axboe [this message]
2017-06-20 0:24 ` Al Viro
2017-06-20 7:20 ` Christoph Hellwig
2017-06-20 11:53 ` Goldwyn Rodrigues
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=1de9d545-8811-4dfa-22db-f5172f122a95@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=rgoldwyn@suse.de \
--cc=viro@ZenIV.linux.org.uk \
/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).