From: Bruce Richardson <bruce.richardson@intel.com>
To: Saurabh Mishra <saurabh.globe@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK mbuf pool in SR-IOV env and one RX/TX queue
Date: Sat, 23 Jan 2016 08:09:31 -0800 [thread overview]
Message-ID: <20160123160930.GA16304@bricha3-MOBL3> (raw)
In-Reply-To: <CAMnwyJ0o9GtjOPxN_=RKHWTKgkeUSeuAFyc7By8KA3rRwnKwNg@mail.gmail.com>
On Thu, Jan 21, 2016 at 08:35:20PM -0800, Saurabh Mishra wrote:
> Hi,
>
>
> Is it possible for two or more processes to share the same mbuf_pool in
> SR-IOV with single rx/tx queue?
>
>
The sharing of the mbuf pool is not an issue, but sharing of rx/tx queues is.
The ethdev queues are not multi-thread safe, so to share a queue between processes
or threads, you need to put in locks or other access control mechanisms. [This
also implies a performance hit due to the locking]
Regards,
/Bruce
next prev parent reply other threads:[~2016-01-23 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 4:35 Saurabh Mishra
2016-01-23 16:09 ` Bruce Richardson [this message]
2016-01-26 0:15 ` Saurabh Mishra
2016-01-26 20:18 ` Bruce Richardson
2016-01-28 4:39 ` Saurabh Mishra
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=20160123160930.GA16304@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=saurabh.globe@gmail.com \
/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).