From: Matthew Wilcox <willy@infradead.org>
To: Dmitry Monakhov <dmtrmonakhov@yandex-team.ru>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
stable@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH] io_uring: Try to merge io requests only for regular files
Date: Fri, 19 Mar 2021 14:06:22 +0000 [thread overview]
Message-ID: <20210319140622.GA3420@casper.infradead.org> (raw)
In-Reply-To: <20210319052859.3220-1-dmtrmonakhov@yandex-team.ru>
On Fri, Mar 19, 2021 at 05:28:59AM +0000, Dmitry Monakhov wrote:
> Otherwise we may endup blocking on pipe or socket.
>
> Fixes: 6d5d5ac ("io_uring: extend async work merge")
7 bytes of sha1 isn't enough. You can set core.abbrev to 12 or upgrade
to a version of git from this decade to get that automatically.
> 2.7.4
... is from 2016, so you're five years out of date. Don't get cut
off when git switches from SHA1.
prev parent reply other threads:[~2021-03-19 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 5:28 [PATCH] io_uring: Try to merge io requests only for regular files Dmitry Monakhov
2021-03-19 6:36 ` Greg KH
2021-03-19 7:45 ` Dmitry Monakhov
2021-03-19 10:23 ` Pavel Begunkov
2021-03-19 14:06 ` Matthew Wilcox [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=20210319140622.GA3420@casper.infradead.org \
--to=willy@infradead.org \
--cc=axboe@kernel.dk \
--cc=dmtrmonakhov@yandex-team.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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).