Hi all,
I wonder if there is any means in DPDK to perform link discovery.
I know that DPDK is all about packet I/O, but maybe there is some library
with useful functions that an application could use for link discovery
(e.g., using LLDP).
Any suggestions are much appreciated.
Thanks,
--
Georgios
Hi,
I am testing rte flow API across different DPDK-based NICs using some rules.
I noticed that flow rules that match L2 information, such as rule:
flow create 0 ingress pattern eth type is 0x800 / end actions queue index 6
/ end
does not work on an Intel 82599ES (igb_uio driver), while a
Mellan
Hi again,
I decided to simplify things for now, hence sent a new minimal patch
only for testpmd (not librte_cmdline), which allows external
applications to compile against it without errors.
Thanks again for you time,
Georgios
On Tue, Jan 16, 2018 at 6:54 PM, Adrien Mazarguil
wrote:
> On Tue, J
Hi Adrien,
Thanks for your insights and sorry for omitting the cover letter (this is
my first patch in DPDK).
I understand your concerns. The reason I proposed this patch is to
facilitate a more high level vendor agnostic API for configuring and
monitoring DPDK-based NICs.
To avoid just copying t
Hi Lu, Oliver,
Thanks for your feedback!
You have a point here, flow commands are only a subset of the parser.
Do you want me to create this new library and send another patch?
I guess I have to use librte_cmdline as a template/example for creating the
librte_flow_cmdline library.
Best regards,
G
Hi Gaetan,
Thanks for your quick and positive reply, I will submit a patch today.
Best regards,
Georgios
On Fri, Jan 12, 2018 at 11:38 AM, Gaƫtan Rivet
wrote:
> Hi George,
>
> On Fri, Jan 12, 2018 at 10:21:41AM +0100, george@gmail.com wrote:
> > Dear DPDK developers,
> >
> > In an attempt
Dear DPDK developers,
In an attempt to integrate the Flow API into a third party application and
allow the e.g., insertion/deletion of NIC classification rules from that
application, I noticed that flow command parsing as per the most recent
DPDK versions (i.e., 17.08 or 17.11) might benefit from
Hi Shahaf,
Thanks for the clarification!
Is there a plan for this functionality to be provided (soon)? (or any
technical limitation that stands in this way)
Thanks and best regards,
Georgios
On Mon, Jan 9, 2017 at 2:32 PM, Shahaf Shuler wrote:
> Hi Georgios,
>
> It is not support on Mellanox P
Hi,
I have a simple setup with a machine that contains a dual port 10 GbE Intel
82599ES NIC and another dual port 100 GbE Mellanox ConnectX-4 NIC. The
Intel ports are 0 and 1, while the Mellanox ones are 2 and 3.
I properly compiled DPDK 16.11 and test-pmd works just fine for all 4 ports.
Then, I
Hi again,
I have a follow up question. I noticed that when I compile DPDK with
CONFIG_RTE_LIBRTE_MLX5_PMD=y, the compilation fate depends upon the OFED
version that I have.
To become more clear, with DPDK 16.11 and OFED 3.4-2.0.0.0 it compiles, but
DPDK 16.07 and the same OFED fails with:
== Buil
Hi Olga,
That was the issue indeed, thank you very much!
Best regards,
Georgios
On Sat, Dec 17, 2016 at 10:26 PM, Olga Shern wrote:
> Hi Georgios,
>
> Did you install MLNX_OFED?
> You probably missing libmlx5-devel package
>
> Best Regards,
> Olga
>
> -Original Message-
> From: dev [ma
Hi all,
I am coming back to you regarding the Mellanox Connectx4 100Gbps DPDK
driver.
We exchanged some e-mails last summer and I managed to compile the
DPDK-based Mellanox driver using DPDK 16.07 on top of Ubuntu server
16.04.01.
A few days ago, I installed a fresh Ubuntu server 16.04.1 on my ma
12 matches
Mail list logo