From: 최익성 <pnk003@naver.com>
To: ChoiSy Jong <sy.jong.choi@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] Questions about rte_eth_dev multiple rx queue selection (~/dpdk/lib/librte_ether).
Date: Wed, 18 Nov 2015 15:47:04 +0900 (KST) [thread overview]
Message-ID: <f8671fc2df47a2b1dd7fc0bceb25f8a@cweb29.nm.nhnsystem.com> (raw)
In-Reply-To: <697F8B1B48670548A5BAB03E8283550F368232DD@PGSMSX108.gar.corp.intel.com>
Dear Choi, Sy Jong.
Thank you very much for your advice and answer.
I will read and check it.
Sincerely Yours,
Ick-Sung Choi.
-----Original Message-----
From: "Choi, Sy Jong"<sy.jong.choi@intel.com>
To: "최익성"<pnk003@naver.com>; "dev@dpdk.org"<dev@dpdk.org>;
Cc:
Sent: 2015-11-18 (수) 15:43:11
Subject: RE: [dpdk-dev] Questions about rte_eth_dev multiple rx queue selection (~/dpdk/lib/librte_ether).
Hi Mr. Choi,
Please refer to testpmd, we demonstrate filtering to a selected queue.
There are plenty of functions that allow you to select a queue:-
Exp:-
Add or delete a L2 Ethertype filter, which identify packets by their L2 Ethertype mainly assign
them to a receive queue.
ethertype_filter (port_id) (add|del) (mac_addr|mac_ignr) (mac_address) ethertype
(ether_type) (drop|fwd) queue (queue_id)
The available information parameters are:
• port_id: the port which the Ethertype filter assigned on.
• mac_addr: compare destination mac address.
• mac_ignr: ignore destination mac address match.
• mac_address: destination mac address to match.
• ether_type: the EtherType value want to match, for example 0x0806 for ARP packet.
0x0800 (IPv4) and 0x86DD (IPv6) are invalid.
• queue_id : The receive queue associated with this EtherType filter. It is meaningless
when deleting or dropping.
There are 2tuple,5tuple,syn, flex filters and flow director
Regards,
Choi, Sy Jong
Platform Application Engineer
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ???
Sent: Wednesday, November 18, 2015 2:28 PM
To: dev@dpdk.org
Subject: [dpdk-dev] Questions about rte_eth_dev multiple rx queue selection (~/dpdk/lib/librte_ether).
Dear DPDK experts.
I really appreciate for your precious answers and advices and thank you for your great contributions.
I have questions about rte_eth_dev multiple rx queue usage (~/dpdk/lib/librte_ether).
Please let me know, if I am wrong or I have something missed.
The applications use rte_eth_dev_configure( port, n_rx_queues, n_tx_queues, &port_conf) to setup multiple rx queues for a port.
How can we select rx queues for the packets from a port? Is there any rx queue selection function?
Is it determined by NIC and is the rx queue information delivered to DPDK?
I will appreciate to you if I can be given any answer, advice, and comments.
Thank you very much.
Sincerely Yours,
Ick-Sung Choi.
next parent reply other threads:[~2015-11-18 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9f406f6f14e4b65f76bc4944bee492c@cweb19.nm.nhnsystem.com>
[not found] ` <697F8B1B48670548A5BAB03E8283550F368232DD@PGSMSX108.gar.corp.intel.com>
2015-11-18 6:47 ` 최익성 [this message]
[not found] ` <F35DEAC7BCE34641BA9FAC6BCA4A12E70A94BEFA@SHSMSX104.ccr.corp.intel.com>
2015-11-18 6:52 ` 최익성
2015-11-18 7:37 ` Zhang, Helin
2015-11-18 7:40 ` 최익성
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=f8671fc2df47a2b1dd7fc0bceb25f8a@cweb29.nm.nhnsystem.com \
--to=pnk003@naver.com \
--cc=dev@dpdk.org \
--cc=sy.jong.choi@intel.com \
/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).