From: Stephen Hemminger <stephen@networkplumber.org>
To: chen_lp <chen_lp@neusoft.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Does the rte_eth_tx_burst() function is multi-threaded safe when sending pkt in same port and same queue ?
Date: Wed, 8 Jan 2014 22:28:20 -0800 [thread overview]
Message-ID: <CAOaVG17y3NUDzFnVAvxz=oaqFojnyX=vC2wrmxkYTVTRjV=NoA@mail.gmail.com> (raw)
In-Reply-To: <52CE22B7.8040904@neusoft.com>
The rx and tx functions are safe only if a queue is not shared by
multiple threads (or the threads synchronize through some other
mechanism). The safest design is to only use a queue on a single core.
You will see different architectures in the examples. Some use one
queue per core, and others use separate receive and transmit cores.
On Wed, Jan 8, 2014 at 8:16 PM, chen_lp <chen_lp@neusoft.com> wrote:
>
> ---------------------------------------------------------------------------------------------------
> Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
> is intended only for the use of the intended recipient and may be confidential and/or privileged of
> Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is
> not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying
> is strictly prohibited, and may be unlawful.If you have received this communication in error,please
> immediately notify the sender by return e-mail, and delete the original message and all copies from
> your system. Thank you.
> ---------------------------------------------------------------------------------------------------
next prev parent reply other threads:[~2014-01-09 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 4:16 chen_lp
2014-01-09 6:28 ` Stephen Hemminger [this message]
2014-01-09 6:50 ` 金健
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='CAOaVG17y3NUDzFnVAvxz=oaqFojnyX=vC2wrmxkYTVTRjV=NoA@mail.gmail.com' \
--to=stephen@networkplumber.org \
--cc=chen_lp@neusoft.com \
--cc=dev@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).