From: "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"Phil Yang (Arm Technology China)" <Phil.Yang@arm.com>
Subject: [dpdk-users] i40e vPMD fix out of order Rx read issue
Date: Thu, 25 Jul 2019 09:56:38 +0000 [thread overview]
Message-ID: <VI1PR08MB5376E32395B5B2A3D63D8EAF8FC10@VI1PR08MB5376.eurprd08.prod.outlook.com> (raw)
Hi Qi,
I am working on optimizing the i40e vPMD on aarch64 and I see this patch relevant.
Could you illuminate what issue this patch was fixing?
I understand the PMD works at the driver layer, for delivery of L2 packets.
It does not own the responsibility to keep order(the responsibility lies with the protocol stack, like TCP)?
http://patches.dpdk.org/patch/16665/
Best regards,
Gavin
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next reply other threads:[~2019-07-25 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:56 Gavin Hu (Arm Technology China) [this message]
2019-07-25 12:11 ` Zhang, Qi Z
2019-07-26 10:00 ` Gavin Hu (Arm Technology China)
2019-07-27 1:32 ` Zhang, Qi Z
2019-08-14 3:19 ` Gavin Hu (Arm Technology China)
2019-08-14 3:38 ` Zhang, Qi Z
2019-08-16 2:50 ` Ye Xiaolong
2019-08-16 3:44 ` Zhang, Qi Z
2019-08-16 6:24 ` Gavin Hu (Arm Technology China)
2019-08-26 6:11 ` Honnappa Nagarahalli
2019-08-26 15:55 ` Honnappa Nagarahalli
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=VI1PR08MB5376E32395B5B2A3D63D8EAF8FC10@VI1PR08MB5376.eurprd08.prod.outlook.com \
--to=gavin.hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Phil.Yang@arm.com \
--cc=bruce.richardson@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=users@dpdk.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).