DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: 최익성 <pnk003@naver.com>, "dev@dpdk.org" <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 07:37:14 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A94BF7D@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <e9b1267c4c39d6ab6b8f4f563878b72@cweb16.nm.nhnsystem.com>

RSS and redirection table is popular features in almost all NICs, so you can refer to NIC datasheet or google.
It is easy to find out good articles.

Regards,
Helin

From: 최익성 [mailto:pnk003@naver.com]
Sent: Wednesday, November 18, 2015 2:53 PM
To: Zhang, Helin; dev@dpdk.org
Subject: RE: [dpdk-dev] Questions about rte_eth_dev multiple rx queue selection (~/dpdk/lib/librte_ether).


Dear Zhang, Helin.



Thank you very much for your advice and answer.



I guess RSS queue selection is performed in NIC.



Would you tell me more about redirection table?  Where can I find reference for it?



Thank you very much.



Sincerely Yours,



Ick-Sung Choi.



-----Original Message-----
From: "Zhang, Helin"<helin.zhang@intel.com>
To: "최익성"<pnk003@naver.com>; "dev@dpdk.org"<dev@dpdk.org>;
Cc:
Sent: 2015-11-18 (수) 15:49:30
Subject: RE: [dpdk-dev] Questions about rte_eth_dev multiple rx queue selection (~/dpdk/lib/librte_ether).

You can refer to 'RSS' and 'redirection table' first.

/Helin

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org]<mailto:[mailto:dev-bounces@dpdk.org]> On Behalf Of ???
> Sent: Wednesday, November 18, 2015 2:28 PM
> To: dev@dpdk.org<mailto: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.
[http://mail.naver.com/readReceipt/notify/?img=b9YqKAIOWNgZK6UlpxmsFo%2BoFzKqa6trM6UrMoC4FzM9FoK%2FFqCSFqigMX%2B0Mour74lR74lcWNFlbX30WLloWrdQarC0Wz057NGcM6lNtz05%2Bzkn74FTWt%3D%3D.gif]



  reply	other threads:[~2015-11-18  7:37 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   ` 최익성
     [not found] ` <F35DEAC7BCE34641BA9FAC6BCA4A12E70A94BEFA@SHSMSX104.ccr.corp.intel.com>
2015-11-18  6:52   ` 최익성
2015-11-18  7:37     ` Zhang, Helin [this message]
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A94BF7D@SHSMSX104.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=pnk003@naver.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).