From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>,
Mikulas Patocka <mpatocka@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mike Snitzer <msnitzer@redhat.com>,
Damien Le Moal <dlemoal@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Guangwu Zhang <guazhang@redhat.com>,
dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] completion: move blk_wait_io to kernel/sched/completion.c
Date: Thu, 18 Apr 2024 08:30:14 -0600 [thread overview]
Message-ID: <5f3d434b-e05c-445f-bee5-2bb1f11a5946@kernel.dk> (raw)
In-Reply-To: <ZiCoIHFLAzCva2lU@infradead.org>
On 4/17/24 10:57 PM, Christoph Hellwig wrote:
> On Wed, Apr 17, 2024 at 08:00:22PM +0200, Mikulas Patocka wrote:
>>>> +EXPORT_SYMBOL(wait_for_completion_long_io);
>>>
>>> Urgh, why is it a sane thing to circumvent the hang check timer?
>>
>> The block layer already does it - the bios can have arbitrary size, so
>> waiting for them takes arbitrary time.
>
> And as mentioned the last few times around, I think we want a task
> state to say that task can sleep long or even forever and not propagate
> this hack even further.
It certainly is a hack/work-around, but unless there are a lot more that
should be using something like this, I don't think adding extra core
complexity in terms of a special task state (or per-task flag, at least
that would be easier) is really warranted.
--
Jens Axboe
next prev parent reply other threads:[~2024-04-18 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 17:49 [PATCH 1/2] completion: move blk_wait_io to kernel/sched/completion.c Mikulas Patocka
2024-04-17 17:55 ` Peter Zijlstra
2024-04-17 18:00 ` Mikulas Patocka
2024-04-18 4:57 ` Christoph Hellwig
2024-04-18 14:30 ` Jens Axboe [this message]
2024-04-18 14:46 ` Christoph Hellwig
2024-04-18 15:09 ` Jens Axboe
2024-04-22 10:59 ` Peter Zijlstra
2024-04-23 12:36 ` Mikulas Patocka
2024-04-26 6:06 ` Christoph Hellwig
2024-04-22 10:54 ` Peter Zijlstra
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=5f3d434b-e05c-445f-bee5-2bb1f11a5946@kernel.dk \
--to=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=guazhang@redhat.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=mpatocka@redhat.com \
--cc=msnitzer@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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 read-only IMAP folder(s) and NNTP newsgroup(s).