From: Gilad Berman <giladb@mellanox.com>
To: Harold Demure <harold.demure87@gmail.com>,
Olga Shern <olgas@mellanox.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 2.2 MLX4: problem with number of TX/RX queues
Date: Thu, 18 Feb 2016 10:31:00 +0000 [thread overview]
Message-ID: <AM2PR05MB0675607F1CCE488F27ECB242A0AF0@AM2PR05MB0675.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <CAKbMwWoVt+WDyWGFhSmM8zgm4A6_wtLq=fn0wp3=H_N7t9PP3w@mail.gmail.com>
Harold,
Flow Director features will be supported only on ConnectX-4 (starting from MLNX_DPDK version to be released end of Feb and on).
So sadly you can't use it with mlx4 (ConnectX-3).
I answered also the community question, btw.
Gilad Berman | Staff System Engineer | Business Development | Mellanox Technologies Ltd.
Work: +972 52 2554262| 6 Ha’Barzel St. Tel Aviv 6971010, Israel
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of Harold Demure
Sent: Tuesday, February 16, 2016 6:05 PM
To: Olga Shern <olgas@mellanox.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] DPDK 2.2 MLX4: problem with number of TX/RX queues
Dear Olga and Vincent,
thank you for your reply.
It seems that the problem has now gone away; both with the -j and without the -j flag. I will try to backtrace the root cause of the problem and report it if I manage to isolate it.
If I may, I would also like to ask your help for a related problem, which I have reported also on the mellanox community forum. If you are available, you may find my question there [1].
I take the occasion to specifically address Olga Shern because I saw that she has already given support on a related topic [2].
Also, related to [2] but possibly un-related from the questions in [1], I am failing to attach a "Perfect Match" filter to my mlx4 NIC, via
rte_eth_dev_filter_ctrl(port_id, RTE_ETH_FILTER_FDIR, RTE_ETH_FILTER_ADD, &filter)
Is this an expected behavior, namely, mlx4 does not support (yet) this kind of operational mode?
Thank you (and anybody willing to help) for your time.
Best regards,
Harold Demure
[1] https://community.mellanox.com/thread/3152
[2] http://dpdk.org/ml/archives/dev/2015-April/016392.html
2016-02-15 9:59 GMT+01:00 Olga Shern <olgas@mellanox.com>:
> Hi Harold,
>
> DPDK 2.2 with MLNX_OFED that you are using and ConnectX-3 support RSS
> automatically.
> You don’t need to configure anything.
>
> Looks there is some bug in the compilation, did you compile with make
> -j, we saw some issue with it.
> Can you please try without -j flag.
>
> Best Regards,
> Olga
>
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Harold Demure
> Sent: Thursday, February 11, 2016 11:37 PM
> To: Vincent Li
> Cc: users@dpdk.org
> Subject: Re: [dpdk-users] DPDK 2.2 MLX4: problem with number of TX/RX
> queues
>
> Hello Vincent,
> Thank you for your reply. I followed the same reasoning as you did,
> looking at the source code earlier today.
>
> Can you send me a link that explains how to change RX for my NIC?
> I have been looking around for that, and also performed the steps in
> the DPDK official guide for MLX4, but apparently nothing changed (at
> least, the error was still there).
>
> In addition, I have to describe a new strange behavior: even *without
> changing anything rss-wise*, but just enabling the increased debugging
> verbosity (CONFIG_RTE_LIBRTE_MLX4_DEBUG=y), the error I had suddenly
> disappeared.
>
> I cannot really explain what happened. Can anybody?
>
> At this point (with the debug prints), now my code blocks because
> apparently mlx4 does not support FlowDir, so I have to change a bit my
> software, which is built to use it.
>
> Still, I would love to know what's going on with my rx/tx queues.
>
> Thank you.
> Regards,
> Harold
>
> 2016-02-11 20:10 GMT+01:00 Vincent Li <vincent.mc.li@gmail.com>:
>
> > On Thu, Feb 11, 2016 at 6:24 AM, Non Voglio
> > <harold.demure87@gmail.com>
> > wrote:
> > > Hello,
> > > I am new to the DPDK world and I am having some troubles in
> > > using some code (not written by me).
> > >
> > > In particular, I bump into this error when invoking the
> > rte_eth_dev_configure
> > > function:
> > >
> > > PMD: librte_pmd_mlx4: 0x10a4d2a0: TX queues number update: 0 -> 16
> > >
> > > PMD: librte_pmd_mlx4: 0x10a4d2a0: RX queues number update: 0 -> 16
> > >
> > > PMD: librte_pmd_mlx4: 0x10a4d2a0: only a single RX queue can be
> > configured
> > > when hardware doesn't support RSS
> > >
> >
> > it appears you must enable RSS support to use multiple RX queue
> >
> > if (!priv->hw_rss) {
> > ERROR("%p: only a single RX queue can be configured when"
> > " hardware doesn't support RSS",
> > (void *)dev);
> > return EINVAL;
> > }
> >
> > Vincent
> >
>
next prev parent reply other threads:[~2016-02-18 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 14:24 Non Voglio
2016-02-11 19:10 ` Vincent Li
2016-02-11 21:36 ` Harold Demure
2016-02-11 22:57 ` Vincent Li
2016-02-15 8:59 ` Olga Shern
2016-02-16 16:04 ` Harold Demure
2016-02-18 10:31 ` Gilad Berman [this message]
2016-02-19 20:01 ` Harold Demure
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=AM2PR05MB0675607F1CCE488F27ECB242A0AF0@AM2PR05MB0675.eurprd05.prod.outlook.com \
--to=giladb@mellanox.com \
--cc=harold.demure87@gmail.com \
--cc=olgas@mellanox.com \
--cc=users@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).