From: Jens Axboe <axboe@kernel.dk>
To: Wen Yang <wenyang.linux@foxmail.com>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Eric Biggers <ebiggers@google.com>,
Christoph Hellwig <hch@lst.de>, Dylan Yudaken <dylany@fb.com>,
David Woodhouse <dwmw@amazon.co.uk>, Fu Wei <wefu@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Michal Nazarewicz <m.nazarewicz@samsung.com>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: Re: [RESEND PATCH v2] eventfd: use wait_event_interruptible_locked_irq() helper
Date: Wed, 5 Apr 2023 13:54:56 -0600 [thread overview]
Message-ID: <f539e49e-d831-2ab1-6344-f37f909895ea@kernel.dk> (raw)
In-Reply-To: <tencent_1A9532B54AD0FB644D7A28B39C5FF9B34506@qq.com>
On 4/5/23 1:40 PM, Wen Yang wrote:
>
> 在 2023/4/6 03:26, Jens Axboe 写道:
>> On 4/5/23 1:20 PM, wenyang.linux@foxmail.com wrote:
>>> From: Wen Yang <wenyang.linux@foxmail.com>
>>>
>>> wait_event_interruptible_locked_irq was introduced by commit 22c43c81a51e
>>> ("wait_event_interruptible_locked() interface"), but older code such as
>>> eventfd_{write,read} still uses the open code implementation.
>>> Inspired by commit 8120a8aadb20
>>> ("fs/timerfd.c: make use of wait_event_interruptible_locked_irq()"), this
>>> patch replaces the open code implementation with a single macro call.
>>>
>>> No functional change intended.
>> Looks pretty reasonable to me. How did you test it?
>>
> Thanks.
>
> We have verified it in some local testing environments, and the intel-lab-lkp has also tested it more than a month, as follows:
>
> https://github.com/intel-lab-lkp/linux/tree/wenyang-linux-foxmail-com/eventfd-use-wait_event_interruptible_locked_irq-helper/20230217-023039
Nice, you can add my:
Reviewed-by: Jens Axboe <axboe@kernel.dk>
to it as well. Adding Christian as well, as I guess this should go
through his/al/vfs tree.
--
Jens Axboe
next prev parent reply other threads:[~2023-04-05 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 19:20 wenyang.linux
2023-04-05 19:26 ` Jens Axboe
2023-04-05 19:40 ` Wen Yang
2023-04-05 19:54 ` Jens Axboe [this message]
2023-04-06 9:08 ` Christian Brauner
2023-04-05 23:42 wenyang.linux
2023-04-06 15:03 ` Christian Brauner
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=f539e49e-d831-2ab1-6344-f37f909895ea@kernel.dk \
--to=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=dylany@fb.com \
--cc=ebiggers@google.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.nazarewicz@samsung.com \
--cc=pbonzini@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wefu@redhat.com \
--cc=wenyang.linux@foxmail.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®