From: Olivier Matz <olivier.matz@6wind.com>
To: "Chandran, Sugesh" <sugesh.chandran@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
Maxime Leroy <maxime.leroy@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] ixgbe: support checksum flags in sse vector Rx function
Date: Tue, 19 Jul 2016 17:51:31 +0200 [thread overview]
Message-ID: <61364fe7-344f-5cb8-8411-87bd234428ce@6wind.com> (raw)
In-Reply-To: <2EF2F5C0CC56984AA024D0B180335FCB13DEDCB2@IRSMSX102.ger.corp.intel.com>
Hi Sugesh,
On 07/14/2016 11:24 AM, Chandran, Sugesh wrote:
> Hi Olivier,
> Thank you for working on this.
> We tried to enable checksum offload in OVS-DPDK and couldn't proceed due to the performance impact.
> I assume this patch will fix that issue by enabling checksum offloading with vectorization ON at Rx side.
>
> Few questions,
> 1) Is there any plan to extend this to other NIC drivers, other than ixgbe? What are the implications of it?
On my side no plan for other drivers, but this is more a question for
pmd maintainers.
> 2) Is it possible to enable it on the Tx side as well?
Yes, vector tx is enabled or not depending on the feature you request at
init (offload, multisegments, ...). See ixgbe_set_tx_function() for
details. My patch does not change this behavior.
>
> I haven't looked into patch very detail and very little context on it. So please forgive me if any of these queries make no sense.
>
> Regards
> _Sugesh
Regards,
Olivier
next prev parent reply other threads:[~2016-07-19 15:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 12:19 Olivier Matz
2016-07-08 20:42 ` Bruce Richardson
2016-07-10 17:41 ` Olivier Matz
2016-07-14 9:24 ` Chandran, Sugesh
2016-07-19 15:51 ` Olivier Matz [this message]
2016-09-14 12:39 ` Ferruh Yigit
2016-10-06 14:00 ` [dpdk-dev] " Remy Horton
2016-10-13 23:27 ` Thomas Monjalon
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=61364fe7-344f-5cb8-8411-87bd234428ce@6wind.com \
--to=olivier.matz@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=maxime.leroy@6wind.com \
--cc=sugesh.chandran@intel.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).