DPDK patches and discussions
 help / color / mirror / Atom feed
From: =?gb18030?B?1ebO0rfnssk=?= <1534057243@qq.com>
To: =?gb18030?B?ZGV2?= <dev@dpdk.org>
Subject: [dpdk-dev]  rte_vhost_enqueue/dequeue_brust thread safely?
Date: Wed, 17 Jan 2018 15:30:20 +0800	[thread overview]
Message-ID: <tencent_B8B03AA96F6CF74A517C96260A0F4FDBB505@qq.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 524 bytes --]

Hi, ALL: 
1. for api "rte_vhost_dequeue_burst", is it safely called from muitiple thread/process on 17.11?, just as single-produce multiple consume


2. for api "rte_vhost_enqueue_burst", is it safely called from muitiple thread/process on 17.11? just as multi-produce single consume


3. I find that "The function rte_vhost_enqueue_burst no longer supports concurrent enqueuing packets to the same queue"  from release nodes of dpdk16.07, why not support  this?  perfermance issue or other reasons? 




thanks!

                 reply	other threads:[~2018-01-17  7:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=tencent_B8B03AA96F6CF74A517C96260A0F4FDBB505@qq.com \
    --to=1534057243@qq.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).