From: David Miller <davem@davemloft.net>
To: Jon.Zhou@jdsu.com
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: packet received in a wrong rx-queue?
Date: Wed, 18 May 2011 05:13:37 -0400 (EDT) [thread overview]
Message-ID: <20110518.051337.1758997463750600514.davem@davemloft.net> (raw)
In-Reply-To: <4A6A2125329CFD4D8CC40C9E8ABCAB9F250D748939@MILEXCH2.ds.jdsu.net>
From: Jon Zhou <Jon.Zhou@jdsu.com>
Date: Wed, 18 May 2011 02:00:50 -0700
> There are 2 packets in the traffic
>
> #1 create PDP context request, IPV4--UDP--GTP, src_ip=A and dst_ip=B,src_port=C,dst_port=D
>
> #2 create PDP context response, IPV4--UDP--GTP,src_ip=B, dst_ip=A, src_port=D,dst_port=C
>
> I suppose both of them will be received in same rx-queue but actually it doesn't
Well, for hardware flow steering, it's not expected to.
next prev parent reply other threads:[~2011-05-18 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 9:00 packet received in a wrong rx-queue? Jon Zhou
2011-05-18 9:13 ` David Miller [this message]
2011-05-19 1:26 ` Jon Zhou
2011-05-19 1:32 ` David Miller
2011-05-19 3:22 ` Jon Zhou
2011-05-19 3:36 ` David Miller
2011-05-20 1:48 ` Jon Zhou
2011-05-20 3:12 ` 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=20110518.051337.1758997463750600514.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Jon.Zhou@jdsu.com \
--cc=e1000-devel@lists.sourceforge.net \
--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).