From: Jens Axboe <[email protected]>
To: Jiufei Xue <[email protected]>, [email protected]
Cc: [email protected]
Subject: Re: [PATCH v2] io_uring: add EPOLLEXCLUSIVE flag to aoid thundering herd type behavior
Date: Thu, 11 Jun 2020 09:07:57 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/10/20 10:30 PM, Jiufei Xue wrote:
> From: Jiufei Xue <[email protected]>
>
> Applications can use this flag to avoid accept thundering herd.
> And poll_events should be changed to 32 bits to cover EPOLLEXCLUSIVE.
>
> Signed-off-by: Jiufei Xue <[email protected]>
Both of your patches seem to have a weird setup where the
From is alibaba.linux.com, and the SOB is linux.alibaba.com.
I'm assuming the latter is the correct one, as that's where
the email came from and the former doesn't have an MX record.
This is 5.9 material for me. With the above fixed up, please
turn this into a series where 1/2 is changing the poll type
to be 32-bits, and 2/2 is the functional change that is in
this patch.
--
Jens Axboe
prev parent reply other threads:[~2020-06-11 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 4:30 [PATCH v2] io_uring: add EPOLLEXCLUSIVE flag to aoid thundering herd type behavior Jiufei Xue
2020-06-11 15:07 ` Jens Axboe [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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