From: Neil Horman <nhorman@tuxdriver.com>
To: Matthew Hall <mhall@mhcomputing.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH RFC] librte_reorder: new reorder library
Date: Wed, 8 Oct 2014 18:55:41 -0400 [thread overview]
Message-ID: <20141008225540.GA15850@hmsreliant.think-freely.org> (raw)
In-Reply-To: <20141008224111.GC29243@mhcomputing.net>
On Wed, Oct 08, 2014 at 03:41:11PM -0700, Matthew Hall wrote:
> On Tue, Oct 07, 2014 at 09:33:06AM +0000, Pattan, Reshma wrote:
> > To be used along with distributor library. Next version of distributor are
> > planned to distribute incoming packets to all worker cores irrespective of
> > the flow type. In this case to ensure in order delivery of the packets at
> > output side reorder library will used by the tx end.
>
> Hello,
>
> I am trying to understand, why is usage of the RSS options on the RX Queues
> insufficient to keep the packets ordered per-flow on the TX Queues?
>
I think because there is a possibility that multiple workers may be used for a
single tx queue.
Neil
> Thanks,
> Matthew.
>
next prev parent reply other threads:[~2014-10-08 22:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 9:33 Pattan, Reshma
2014-10-07 11:21 ` Neil Horman
2014-10-08 14:11 ` Pattan, Reshma
2014-10-08 19:15 ` Neil Horman
2014-10-09 10:27 ` Pattan, Reshma
2014-10-09 11:36 ` Neil Horman
2014-10-09 14:36 ` Pattan, Reshma
2014-10-09 16:09 ` Neil Horman
2014-10-09 17:21 ` Matthew Hall
2014-10-09 17:55 ` Neil Horman
2014-10-08 22:41 ` Matthew Hall
2014-10-08 22:55 ` Neil Horman [this message]
2014-10-08 23:07 ` Matthew Hall
2014-10-09 9:14 ` Bruce Richardson
2014-10-09 17:11 ` Matthew Hall
2014-10-10 10:59 ` Bruce Richardson
2014-10-09 19:01 ` Jay Rolette
2014-10-17 9:44 ` Pattan, Reshma
2014-10-17 16:26 ` Jay Rolette
2014-10-18 17:26 ` Matthew Hall
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=20141008225540.GA15850@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=mhall@mhcomputing.net \
/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).