From: Mostafa Salari <msgm68@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] A problem with KNI in pipeline
Date: Sun, 6 Mar 2016 21:35:00 +0330 [thread overview]
Message-ID: <CAGQ+h=2xxR=y00bjx7sWHO0i0y9K4Mbm3Hiy=ZuThv-Jtx2nUg@mail.gmail.com> (raw)
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
next reply other threads:[~2016-03-06 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 18:05 Mostafa Salari [this message]
2016-03-07 12:41 ` Andriy Berestovskyy
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='CAGQ+h=2xxR=y00bjx7sWHO0i0y9K4Mbm3Hiy=ZuThv-Jtx2nUg@mail.gmail.com' \
--to=msgm68@gmail.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).