DPDK usage discussions
 help / color / mirror / Atom feed
From: Pavel Vazharov <freakpv@gmail.com>
To: "Ruslan R. Laishev" <zator@yandex.ru>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Sending/Enqueue a <mbuf> from different threads to single queue --- how to ?
Date: Thu, 26 Jan 2023 13:08:47 +0200	[thread overview]
Message-ID: <CAK9EM19yBa1_+4BFJ7eMt99-74YssSgAjWVqakzK9pu9XU5G9Q@mail.gmail.com> (raw)
In-Reply-To: <945211674729151@mail.yandex.ru>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

On Thu, Jan 26, 2023 at 12:46 PM Ruslan R. Laishev <zator@yandex.ru> wrote:

> Hello!
>
> Continue studying DPDK ...
>
> I have a some nano-task : I'm need to send a packet/mbuf to queue of a
> device from separate worker .
>
> Several workers (every worker run on own lcore) send/receive packets
> to/from queues of devices
> worker #0 ------- port0/que0
>                         - port1/que0
>                         - portN/que0
> worker #1 ------- port0/que1
>                         - port1/que1
>                         - portN/que1
> ...
> worker #N ------- port0/queN
>                         - port1/queN
>                         - portN/queN
>
> There is a yet another thread which want to send mbuf/packet to queue #0
> (just for example) to every device
>

Hi,

I don't think you can inject packets into the device queues.

However, you can achieve the same, sending mbufs between the worker
threads, using the provided ring functionality of DPDK -
http://doc.dpdk.org/guides/prog_guide/ring_lib.html.
The worker threads will need to try to dequeue regularly for the shared
ring(s).

Regards.

[-- Attachment #2: Type: text/html, Size: 2823 bytes --]

  reply	other threads:[~2023-01-26 11:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 10:46 Ruslan R. Laishev
2023-01-26 11:08 ` Pavel Vazharov [this message]
2023-01-26 11:13   ` Ruslan R. Laishev

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=CAK9EM19yBa1_+4BFJ7eMt99-74YssSgAjWVqakzK9pu9XU5G9Q@mail.gmail.com \
    --to=freakpv@gmail.com \
    --cc=users@dpdk.org \
    --cc=zator@yandex.ru \
    /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).