From: Dor Laor <dor@cloudius-systems.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, Vladislav Zolotarov <vladz@cloudius-systems.com>,
Avi Kivity <avi@cloudius-systems.com>,
Gleb Natapov <gleb@cloudius-systems.com>
Subject: Re: [dpdk-dev] DPDK RSS support for ixgbevf PMD
Date: Mon, 15 Dec 2014 22:45:52 +0200 [thread overview]
Message-ID: <CAKUaUn7hH=6NmD524S_iFX_6THiRKRdMrsiLga_3SB_YCEQxNQ@mail.gmail.com> (raw)
In-Reply-To: <6168753.p4Vk7dlKkK@xps13>
On Mon, Dec 15, 2014 at 10:33 PM, Thomas Monjalon <thomas.monjalon@6wind.com
> wrote:
>
> 2014-12-15 21:11, Vladislav Zolotarov:
> > Hi,
> > I'm running an ixgbevf PMD on an AWS guests with extended networking
> > (SR-IOV functions of 82599 Intel's NIC) and noticed that even in the
> > current git tree there is no support for a multi-queue in this PMD: reta
> > size returned by rte_eth_dev_info_get() call is 0, while max_rx_queues
> and
> > max_tx_queues are both 4.
> >
> > Linux ixgbevf-2.15.3 driver on the other hand successfully initializes 2
> > RSS queues: for some reason it always limits the number of RSS queues by
> 2.
> >
> > ixgbevf_main.c: line 2539
> > u16 rss = min_t(u16, num_online_cpus(), 2);
> >
> > The above is strange since if MRQE is set to 1010b there are 4 RSS queues
> > available which seems to be the case in my AWS Guest.
> >
> > However, let's get back to DPDK. As I've mentioned above the SR-IOV
> > function i have is RSS capable (to be 100% sure I've verified both queues
> > are receiving packets in a multi-socket TCP test). And it's a shame I
> can't
> > utilize it with a DPDK.
>
> Yes, it is not yet supported.
> But a patch was recently sent:
> http://dpdk.org/ml/archives/dev/2014-December/010028.html
Good to know and nice timing
>
> t
> > I wonder if there are any blockers to add this capability to the ixgbevf
> > PMD and if not is it scheduled to some time soon?
>
> Please jump in the above thread for your questions.
>
> My turn to ask a question:
> Does it mean DPDK is going to be supported in your system (OSv)?
>
In general yes. It's premature to ask now since there are components
that already implemented in OSv and won't be needed (efficient
producer-consumer, huge pages, etc). We sure like to reuse the driver code,
it's a pity not to contribute to the same code base. We'll certainly like
to let unmodified dpdk apps run as well
Initially we're playing w/ the Linux dpdk on the host and AWS to gain
familiarity w/ it
> I've seen it in the OSv roadmap.
> Could we have more details about how it would be integrated?
>
> Thanks
> --
> Thomas
>
next prev parent reply other threads:[~2014-12-15 20:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 19:11 Vladislav Zolotarov
2014-12-15 20:33 ` Thomas Monjalon
2014-12-15 20:45 ` Dor Laor [this message]
2014-12-15 21:04 ` [dpdk-dev] DPDK on OSv (was: RSS for ixgbevf) Thomas Monjalon
2014-12-15 23:04 ` Dor Laor
2014-12-16 15:36 ` [dpdk-dev] DPDK RSS support for ixgbevf PMD Vlad Zolotarov
2014-12-17 1:03 ` Ouyang, Changchun
2014-12-17 8:46 ` Vlad Zolotarov
2014-12-18 1:32 ` Ouyang, Changchun
2014-12-18 10:33 ` Vlad Zolotarov
2014-12-19 1:17 ` Ouyang, Changchun
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='CAKUaUn7hH=6NmD524S_iFX_6THiRKRdMrsiLga_3SB_YCEQxNQ@mail.gmail.com' \
--to=dor@cloudius-systems.com \
--cc=avi@cloudius-systems.com \
--cc=dev@dpdk.org \
--cc=gleb@cloudius-systems.com \
--cc=thomas.monjalon@6wind.com \
--cc=vladz@cloudius-systems.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).