From: David Miller <davem@davemloft.net>
To: alexander.h.duyck@intel.com
Cc: jeffrey.t.kirsher@intel.com, jesse.brandeburg@intel.com,
bruce.w.allan@intel.com, netdev@vger.kernel.org
Subject: Re: ixgbe: normalize frag_list usage
Date: Mon, 04 Oct 2010 11:32:58 -0700 (PDT) [thread overview]
Message-ID: <20101004.113258.212671454.davem@davemloft.net> (raw)
In-Reply-To: <4CAA1722.7070405@intel.com>
From: Alexander Duyck <alexander.h.duyck@intel.com>
Date: Mon, 04 Oct 2010 11:04:18 -0700
> This will not work for RSC due to the fact that it assumes only one
> RSC context is active per ring and that is not the case. There can be
> multiple RSC combined flows interlaced on the ring.
Thanks for looking at this Alexander.
I must have mis-understood what the current code is doing.
It looked like RSC packets always show up in-order in the RX ring.
And that they are scanned for by simply combining any sequence of
non-EOP packets up to and including the final EOP one into a frag
list.
Are the RSC packets are identified via something else entirely?
next prev parent reply other threads:[~2010-10-04 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 6:54 ixgbe: normalize frag_list usage David Miller
2010-10-04 15:37 ` Rose, Gregory V
2010-10-04 18:04 ` Alexander Duyck
2010-10-04 18:32 ` David Miller [this message]
2010-10-04 19:49 ` Alexander Duyck
2010-10-05 22:45 ` Duyck, Alexander H
2010-10-06 3:08 ` David Miller
2010-10-07 6:58 ` David Miller
2010-10-07 19:59 ` Alexander Duyck
2010-10-14 2:17 ` David Miller
2010-10-08 23:57 ` [RFC] ixgbe: v3 " Duyck, Alexander H
2010-10-25 19:47 ` David Miller
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=20101004.113258.212671454.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.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).