public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: selftest io_uring_zerocopy_tx.sh failed on VM
Date: Mon, 17 Jul 2023 13:34:04 +0100	[thread overview]
Message-ID: <2bf18f5b-9539-e706-b887-3de330950061@gmail.com> (raw)
In-Reply-To: <ZLS/iWz+gF0/PGyR@Laptop-X1>

On 7/17/23 05:11, Hangbin Liu wrote:
> Hi Pavel,
> 
> I tried to run test selftest io_uring_zerocopy_tx.sh on VM, but it failed
> with error like
> 
> + ip netns exec ns-45iLeE2 ./msg_zerocopy -4 -t 2 -C 2 -S 192.168.1.1 -D 192.168.1.2 -r udp
> cpu: unable to pin, may increase variance.
> + ip netns exec ns-45iLeE1 ./io_uring_zerocopy_tx -4 -t 1 -D 192.168.1.2 -m 1 -t 1 -n 32 udp
> ./io_uring_zerocopy_tx: io_uring: queue init: Unknown error -13
> 
> Do you know what's the reason? Should we update the test script to return
> SKIP if io_uring init failed?

I don't recall anything that can fail ring init with EACCES, probably
sth in your system disables io_uring with some syscall filters or so.
I think skipping the trace on EACCES is the right approach. Do you want
to send a patch?
Apart from that, if you're curious you can try to trace what's going on,
ftrace should give an idea.

-- 
Pavel Begunkov

  reply	other threads:[~2023-07-17 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  4:11 selftest io_uring_zerocopy_tx.sh failed on VM Hangbin Liu
2023-07-17 12:34 ` Pavel Begunkov [this message]
2023-07-18  2:10   ` Hangbin Liu

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=2bf18f5b-9539-e706-b887-3de330950061@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.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