From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@canonical.com>
Cc: Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
linux-btrfs@vger.kernel.org,
"open list:FILESYSTEMS (VFS and infrastructure)"
<linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] block: avoid to call .bi_end_io() recursively
Date: Mon, 2 May 2016 07:52:32 -0700 [thread overview]
Message-ID: <20160502145232.GC20589@infradead.org> (raw)
In-Reply-To: <1461805743-3559-1-git-send-email-ming.lei@canonical.com>
On Thu, Apr 28, 2016 at 09:09:00AM +0800, Ming Lei wrote:
> The 3rd patch avoids to call .bi_end_io recursively in complete path.
Care to explain what the reason for doing that is?
If we have excessively long bi_end_io chains we should probably look
into fixing them instead.
prev parent reply other threads:[~2016-05-02 14:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 1:09 [PATCH v3 0/3] block: avoid to call .bi_end_io() recursively Ming Lei
2016-04-28 1:09 ` [PATCH v3 1/3] fs: direct-io: handle error in dio_end_io() Ming Lei
2016-04-28 1:09 ` [PATCH v3 2/3] fs: direct-io: call .bi_end_io via bio_endio() Ming Lei
2016-05-02 14:50 ` Christoph Hellwig
2016-05-03 1:26 ` Ming Lei
2016-04-28 1:09 ` [PATCH v3 3/3] block: avoid to call .bi_end_io() recursively Ming Lei
2016-04-28 15:29 ` Mikulas Patocka
2016-04-28 15:52 ` Ming Lei
2016-04-28 15:58 ` Mikulas Patocka
2016-04-28 16:12 ` Ming Lei
2016-04-28 16:59 ` Mikulas Patocka
2016-04-29 5:50 ` Ming Lei
2016-04-29 8:39 ` Mikulas Patocka
2016-04-29 9:33 ` Ming Lei
2016-04-29 9:59 ` Mikulas Patocka
2016-05-02 16:22 ` Jens Axboe
2016-05-02 14:52 ` Christoph Hellwig [this message]
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=20160502145232.GC20589@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
/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).