From: Kemeng Shi <shikemeng@huaweicloud.com>
To: viro@zeniv.linux.org.uk, brauner@kernel.org, dhowells@redhat.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Two cleanups to pipe
Date: Fri, 29 Sep 2023 00:17:50 +0800 [thread overview]
Message-ID: <20230928161752.142268-1-shikemeng@huaweicloud.com> (raw)
This series tries to remove some unnecessary check in pipe. More details
can be found in respective patches. Thanks!
Kemeng Shi (2):
pipe: remove pipe_full check with wrong head in pipe_write
pipe: avoid repeat check of pipe->readers under pipe_lock
fs/pipe.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
--
2.30.0
next reply other threads:[~2023-09-28 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 16:17 Kemeng Shi [this message]
2023-09-28 16:17 ` [PATCH 1/2] pipe: remove pipe_full check with wrong head in pipe_write Kemeng Shi
2023-09-28 16:17 ` [PATCH 2/2] pipe: avoid repeat check of pipe->readers with pipe lock held Kemeng Shi
-- strict thread matches above, loose matches on Subject: below --
2023-10-08 9:47 [PATCH 0/2] Two cleanups to pipe Kemeng Shi
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=20230928161752.142268-1-shikemeng@huaweicloud.com \
--to=shikemeng@huaweicloud.com \
--cc=brauner@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).