DPDK usage discussions
 help / color / mirror / Atom feed
* [dpdk-users] A problem with KNI in pipeline
@ 2016-03-06 18:05 Mostafa Salari
  2016-03-07 12:41 ` Andriy Berestovskyy
  0 siblings, 1 reply; 2+ messages in thread
From: Mostafa Salari @ 2016-03-06 18:05 UTC (permalink / raw)
  To: users

Hello,
I want to create a pipeline to act as KNI port, called *pipeline_kni*, such
that:

   1. A pipeline_kni instance receives packets from its input ports, then
   deliver them to Linux kernel.
   2. pipeline_kni instance receive packets from linux and put them on
   pipeline output ports.


The problem is that I want to identify actual port id corresponding to a
input port of pipeline! Because I need to pass this information to
rte_eth_dev_info_get(*port_id* , &dev_info) to retrieve NIC information
(such as PCI adrs, ...)

I'm new to using pipeline! Is there any other standard way to do this?

Its a point to KNI in the link below in Table 23.1
<http://dpdk.org/doc/guides/prog_guide/packet_framework.html#table-qos-19>:
http://dpdk.org/doc/guides/prog_guide/packet_framework.html
What does it mean? Is there a pipeline input/output port of type KNI? If
so, how can we determine it (for example) in *pktq_in* field in a
configuration file?

Thanks,
Regards

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [dpdk-users] A problem with KNI in pipeline
  2016-03-06 18:05 [dpdk-users] A problem with KNI in pipeline Mostafa Salari
@ 2016-03-07 12:41 ` Andriy Berestovskyy
  0 siblings, 0 replies; 2+ messages in thread
From: Andriy Berestovskyy @ 2016-03-07 12:41 UTC (permalink / raw)
  To: Mostafa Salari; +Cc: users

Hi Mostafa,
AFAIK DPDK does not support KNI ports, despite the documentation
states it is. In our project we had to implement our own KNI port
reader/writer...

Andriy


On Sun, Mar 6, 2016 at 7:05 PM, Mostafa Salari <msgm68@gmail.com> wrote:
> Hello,
> I want to create a pipeline to act as KNI port, called *pipeline_kni*, such
> that:
>
>    1. A pipeline_kni instance receives packets from its input ports, then
>    deliver them to Linux kernel.
>    2. pipeline_kni instance receive packets from linux and put them on
>    pipeline output ports.
>
>
> The problem is that I want to identify actual port id corresponding to a
> input port of pipeline! Because I need to pass this information to
> rte_eth_dev_info_get(*port_id* , &dev_info) to retrieve NIC information
> (such as PCI adrs, ...)
>
> I'm new to using pipeline! Is there any other standard way to do this?
>
> Its a point to KNI in the link below in Table 23.1
> <http://dpdk.org/doc/guides/prog_guide/packet_framework.html#table-qos-19>:
> http://dpdk.org/doc/guides/prog_guide/packet_framework.html
> What does it mean? Is there a pipeline input/output port of type KNI? If
> so, how can we determine it (for example) in *pktq_in* field in a
> configuration file?
>
> Thanks,
> Regards



-- 
Andriy Berestovskyy

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-03-07 12:41 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-06 18:05 [dpdk-users] A problem with KNI in pipeline Mostafa Salari
2016-03-07 12:41 ` Andriy Berestovskyy

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).