From: Jens Axboe <[email protected]>
To: Reece <[email protected]>, [email protected]
Subject: Re: io_uring is a regression over 16 year old aio/io_submit, 2+ decades of Microsoft NT, and *BSD circa 1997-2001
Date: Thu, 4 May 2023 13:27:31 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 5/4/23 1:20?PM, Reece wrote a pile of garbage.
If you have constructive criticism, the list is open to discuss it.
Sending trolly garbage anonymously is, however, neither welcome nor a
productive approach.
--
Jens Axboe
next prev parent reply other threads:[~2023-05-04 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 19:20 io_uring is a regression over 16 year old aio/io_submit, 2+ decades of Microsoft NT, and *BSD circa 1997-2001 Reece
2023-05-04 19:27 ` Jens Axboe [this message]
[not found] ` <[email protected]>
[not found] ` <[email protected]>
2023-05-04 19:37 ` Reece
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] \
/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