From: Pavel Begunkov <asml.silence@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>, Andres Freund <andres@anarazel.de>
Cc: Jens Axboe <axboe@kernel.dk>,
io-uring@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Darren Hart <dvhart@infradead.org>,
Davidlohr Bueso <dave@stgolabs.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 4/4] io_uring: implement futex wait
Date: Mon, 7 Jun 2021 12:31:48 +0100 [thread overview]
Message-ID: <131a59af-a625-27b3-433e-ff8b7c36753e@gmail.com> (raw)
In-Reply-To: <87v96tywcb.ffs@nanos.tec.linutronix.de>
On 6/5/21 1:43 AM, Thomas Gleixner wrote:
> Andres,
>
> On Thu, Jun 03 2021 at 12:03, Andres Freund wrote:
>> On 2021-06-01 23:53:00 +0200, Thomas Gleixner wrote:
>>> You surely made your point that this is well thought out.
>>
>> Really impressed with your effort to generously interpret the first
>> version of a proof of concept patch that explicitly was aimed at getting
>> feedback on the basic design and the different use cases.
>
> feedback on what?
>
> There is absolutely no description of design and obviously there is no
> use case either. So what do you expect me to be generous about?
That's a complete fallacy, the very RFC is about clarifying a
use case that I was hinted about, not mentioning those I described
you in a reply. Obviously
--
Pavel Begunkov
next prev parent reply other threads:[~2021-06-07 11:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 14:58 [RFC 0/4] futex request support Pavel Begunkov
2021-06-01 14:58 ` [RFC 1/4] futex: add op wake for a single key Pavel Begunkov
2021-06-01 14:58 ` [RFC 2/4] io_uring: frame out futex op Pavel Begunkov
2021-06-01 14:58 ` [RFC 3/4] io_uring: support futex wake requests Pavel Begunkov
2021-06-01 14:58 ` [RFC 4/4] io_uring: implement futex wait Pavel Begunkov
2021-06-01 15:45 ` Jens Axboe
2021-06-01 15:58 ` Pavel Begunkov
2021-06-01 16:01 ` Jens Axboe
2021-06-01 16:29 ` Pavel Begunkov
2021-06-01 21:53 ` Thomas Gleixner
2021-06-03 10:31 ` Pavel Begunkov
2021-06-04 9:19 ` Thomas Gleixner
2021-06-04 11:58 ` Pavel Begunkov
2021-06-05 2:09 ` Thomas Gleixner
2021-06-07 12:14 ` Pavel Begunkov
2021-06-03 19:03 ` Andres Freund
2021-06-03 21:10 ` Peter Zijlstra
2021-06-03 21:21 ` Andres Freund
2021-06-05 0:43 ` Thomas Gleixner
2021-06-07 11:31 ` Pavel Begunkov [this message]
2021-06-07 11:48 ` Peter Zijlstra
2021-06-03 18:59 ` [RFC 0/4] futex request support Andres Freund
2021-06-04 15:26 ` Pavel Begunkov
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=131a59af-a625-27b3-433e-ff8b7c36753e@gmail.com \
--to=asml.silence@gmail.com \
--cc=andres@anarazel.de \
--cc=axboe@kernel.dk \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.