From: Carlos de Souza Moraes Neto <carlosmn@weg.net>
To: David Marchand <david.marchand@redhat.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: RES: Virtio_user for kernel interface.
Date: Tue, 29 Aug 2023 11:04:28 +0000 [thread overview]
Message-ID: <RO2P152MB60082BD1486275B8A1E5B060DDE7A@RO2P152MB6008.LAMP152.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CAJFAV8wjA3jNYwH1bs1W-EENNtmoiZBiqYSgSYi9LB875-VOHQ@mail.gmail.com>
Hi David,
Thankyou it worked.
Sincerely,
Carlos de Souza Moraes Neto
WEG Equipamentos Elétricos S/A. - Transmissão & Distribuição
www.weg.net
-----Mensagem original-----
De: David Marchand <david.marchand@redhat.com>
Enviada em: segunda-feira, 28 de agosto de 2023 05:31
Para: Carlos de Souza Moraes Neto <carlosmn@weg.net>
Cc: users@dpdk.org
Assunto: Re: Virtio_user for kernel interface.
ATENÇÃO: Esta mensagem é de REMETENTE EXTERNO - Tenha cuidado ao abrir links e anexos.
*** NOVO *** NÃO digite sua SENHA WEG quando solicitada por E-MAIL EXTERNO
On Mon, Aug 28, 2023 at 10:07 AM Carlos de Souza Moraes Neto <carlosmn@weg.net> wrote:
> I'm attempting to utilize virtio_user for packet transmission and reception via the kernel's network stack. I transmitted packets from a NIC to virtio_user0 and captured them on the tap0 interface. However, when trying to send a packet from tap0 (for instance, a basic ping) and route it to DPDK, the function rte_eth_rx_burst returns zero packets. My initialization is set as follows:
> -l 0-4 --vdev=virtio_user0,path=/dev/vhost-net,queues=3,queue_size=1024.
Just an idea.
If you ask for 3 queue pairs, your application must poll packets from all 3 rxqs, as the kernel may choose to send packets through any of those queues.
Are you perhaps only polling one rxq?
--
David Marchand
prev parent reply other threads:[~2023-08-29 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 14:47 Carlos de Souza Moraes Neto
2023-08-28 8:30 ` David Marchand
2023-08-29 11:04 ` Carlos de Souza Moraes Neto [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=RO2P152MB60082BD1486275B8A1E5B060DDE7A@RO2P152MB6008.LAMP152.PROD.OUTLOOK.COM \
--to=carlosmn@weg.net \
--cc=david.marchand@redhat.com \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).