From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: dave seddon <dave.seddon.ca@gmail.com>
Cc: FQ Liu <qleex001@gmail.com>, users <users@dpdk.org>,
Nishant Verma <vnish11@gmail.com>
Subject: Re: [dpdk-users] How to use more rx queues than RSS queue limit for ixgbe
Date: Thu, 18 Aug 2016 17:32:26 +0500 [thread overview]
Message-ID: <CAN7yQ2rO8m-PzpLVNDFbhNBBY7Z+dPoQPR3woE96_h=cYb3E5w@mail.gmail.com> (raw)
In-Reply-To: <CANypexTvz8wDBFfbKbS-k0g=BcXWGxs0q7GtSPh5OOacJr+bPg@mail.gmail.com>
But the flow director queues wont matter as the hash against the tuple will
be the same
prev parent reply other threads:[~2016-08-18 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 10:25 FQ Liu
2016-08-16 13:35 ` Nishant Verma
[not found] ` <CAG7SzU69fJTTf2k6hzSAM4cM6obh0-kunQc2=39sOnX4Mhdhag@mail.gmail.com>
2016-08-17 14:40 ` Muhammad Zain-ul-Abideen
2016-08-17 19:49 ` dave seddon
2016-08-18 12:32 ` Muhammad Zain-ul-Abideen [this message]
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='CAN7yQ2rO8m-PzpLVNDFbhNBBY7Z+dPoQPR3woE96_h=cYb3E5w@mail.gmail.com' \
--to=zain2294@gmail.com \
--cc=dave.seddon.ca@gmail.com \
--cc=qleex001@gmail.com \
--cc=users@dpdk.org \
--cc=vnish11@gmail.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).