[dpdk-users] Question about combine libs option
On 18/02/2016 20:10, Arevalo, Mario Alfredo C wrote: > Hi, good day, I have a question related to CONFIG_RTE_BUILD_COMBINE_LIBS > option in DPDK configuration file, > It's not clear for me what is the behavior of this option but it seems that > when I enabled this option > all libraries were combined to one single library called libdpdk.so (I > enabled CONFIG_RTE_BUILD_SHARED_LIB too), > is this correct? That is correct. Now, you can use COMBINE_LIB with or without SHARED_LIB. The result is, as you said, combining all DPDK libraries into a single library. > or which other effects can produce this option, and if someone has a document > about this > option would be amazing :), thank you so much for your attention. I don't think there is any info/doc regarding those config options (someone else can correct me on this), but I would think that the GSG (Getting Started Guide) would be a good place to add such doc. Sergio > Regards. > Mario.
[dpdk-users] Attaching to an ethernet port from a secondary process
Hi, > -Original Message- > From: users [mailto:users-bounces at dpdk.org] On Behalf Of Lazaros Koromilas > Sent: Wednesday, February 17, 2016 11:40 AM > To: users at dpdk.org > Subject: Re: [dpdk-users] Attaching to an ethernet port from a secondary > process > > On Wed, Feb 17, 2016 at 1:17 PM, Lazaros Koromilas > wrote: > > Hi all, > > > > I'm trying to take advantage of the multi-process support together > > with the port hotplugging framework. The idea is that my primary > > process will configure all ports I'm going to need and then secondary > > processes will come up, selectively attach to ports and perform rx/tx.
[dpdk-users] Question about combine libs option
Thank you so much for your help Sergio Regards, Mario. From: Gonzalez Monroy, Sergio Sent: Friday, February 19, 2016 2:48 AM To: Arevalo, Mario Alfredo C Cc: users at dpdk.org Subject: Re: [dpdk-users] Question about combine libs option On 18/02/2016 20:10, Arevalo, Mario Alfredo C wrote: > Hi, good day, I have a question related to CONFIG_RTE_BUILD_COMBINE_LIBS > option in DPDK configuration file, > It's not clear for me what is the behavior of this option but it seems that > when I enabled this option > all libraries were combined to one single library called libdpdk.so (I > enabled CONFIG_RTE_BUILD_SHARED_LIB too), > is this correct? That is correct. Now, you can use COMBINE_LIB with or without SHARED_LIB. The result is, as you said, combining all DPDK libraries into a single library. > or which other effects can produce this option, and if someone has a document > about this > option would be amazing :), thank you so much for your attention. I don't think there is any info/doc regarding those config options (someone else can correct me on this), but I would think that the GSG (Getting Started Guide) would be a good place to add such doc. Sergio > Regards. > Mario.
[dpdk-users] Attaching to an ethernet port from a secondary process
Thanks for your reply Reshma, that clears things up. Lazaros. On Fri, Feb 19, 2016 at 2:58 PM, Pattan, Reshma wrote: > Hi, > >> -Original Message- >> From: users [mailto:users-bounces at dpdk.org] On Behalf Of Lazaros Koromilas >> Sent: Wednesday, February 17, 2016 11:40 AM >> To: users at dpdk.org >> Subject: Re: [dpdk-users] Attaching to an ethernet port from a secondary >> process >> >> On Wed, Feb 17, 2016 at 1:17 PM, Lazaros Koromilas >> wrote: >> > Hi all, >> > >> > I'm trying to take advantage of the multi-process support together >> > with the port hotplugging framework. The idea is that my primary >> > process will configure all ports I'm going to need and then secondary >> > processes will come up, selectively attach to ports and perform rx/tx. > > From quick glance of dpdk code what I see is rte_eth_dev_attach will not > attach existing port to DPDK app. > Because from "librte_ether/rte_ethdev.c" rte_eth_dev_attach()==> > rte_eth_dev_attach_vdev()==>rte_eal_vdev_init() creates new vdev and returns > you the port id. > And moreover vdevs are local to process. > You may have to check clearly what is the hot plug functionality and do you > really need it in your case. > >> > Where pcap{0,1}-in.pcap files are pcap dumps. The primary will >> > initialize the ports and pause(2). The secondary will attach to the >> > same ports and do work. The latter then segfaults in >> > rte_eth_rx_burst() with dev->data->{rx,tx}_queues being NULL pointers. >> > > > Since in secondary new device is created, but device configuration and queue > configuration is not done, crash is expected. > > Thanks, > Reshma
[dpdk-users] DPDK 2.2 MLX4: problem with number of TX/RX queues
Dear Gilad, Let me thank you also here for your kind help. I have replied on the forum. Regards, Harold 2016-02-18 11:31 GMT+01:00 Gilad Berman : > 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 at dpdk.org] On Behalf Of Harold Demure > Sent: Tuesday, February 16, 2016 6:05 PM > To: Olga Shern > Cc: users at 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 : > > > 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 at dpdk.org] On Behalf Of Harold Demure > > Sent: Thursday, February 11, 2016 11:37 PM > > To: Vincent Li > > Cc: users at 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 : > > > > > On Thu, Feb 11, 2016 at 6:24 AM, Non Voglio > > > > > > 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 > > > > > >