From: Victor Stewart <[email protected]>
To: io-uring <[email protected]>
Subject: Re: [POSSIBLE BUG] sendmsg ops returning -ETIME
Date: Fri, 26 Mar 2021 07:26:28 -0400 [thread overview]
Message-ID: <CAM1kxwj9htw+9435L_HiAxW6uNdN+4mUM4wcfv0NLVwez1GeHA@mail.gmail.com> (raw)
In-Reply-To: <CAM1kxwjT66zgh8k=Jnkhn5-UHrBfMjSDyKyrKhuhtCESo9tMew@mail.gmail.com>
On Thu, Mar 25, 2021 at 11:35 PM Victor Stewart <[email protected]> wrote:
> let me know what data i can extract so we can quickly rule this
> definitely my bug or definitely an io-uring bug. it's really the
> bizzare -ETIME that makes me think it might not be mine.
>
> the code is super brief, check perf.networking.cpp
>
> https://github.com/victorstewart/quicperf
haha sorry for the false alarm. within 2 seconds of waking up i
realized that i'm reading past the end of the ring!
prev parent reply other threads:[~2021-03-26 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 3:35 [POSSIBLE BUG] sendmsg ops returning -ETIME Victor Stewart
2021-03-26 11:26 ` Victor Stewart [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 \
--in-reply-to=CAM1kxwj9htw+9435L_HiAxW6uNdN+4mUM4wcfv0NLVwez1GeHA@mail.gmail.com \
[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