From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Stillwell Jr, Paul M" <paul.m.stillwell.jr@intel.com>
Cc: "'dev@dpdk.org'" <dev@dpdk.org>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] net/ice: faster bit check
Date: Thu, 28 Feb 2019 02:04:53 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153344FEE@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E706115333726E@SHSMSX103.ccr.corp.intel.com>
> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Monday, February 18, 2019 8:47 PM
> To: Stillwell Jr, Paul M <paul.m.stillwell.jr@intel.com>
> Cc: dev@dpdk.org; Brandeburg, Jesse <jesse.brandeburg@intel.com>
> Subject: RE: [PATCH v3] net/ice: faster bit check
>
>
>
> > -----Original Message-----
> > From: Stillwell Jr, Paul M
> > Sent: Saturday, February 16, 2019 2:13 AM
> > To: Zhang, Qi Z <qi.z.zhang@intel.com>
> > Cc: dev@dpdk.org; Brandeburg, Jesse <jesse.brandeburg@intel.com>;
> > Stillwell Jr, Paul M <paul.m.stillwell.jr@intel.com>
> > Subject: [PATCH v3] net/ice: faster bit check
> >
> > From: Jesse Brandeburg <jesse.brandeburg@intel.com>
> >
> > Implement a slightly faster bit check, used for checking descriptors
> > in the hot path.
> >
> > Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> > Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
>
> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
The patch is decided to be dropped based on Jesse and Harry's further investigation on the assembly code that compiler generated.
It is removed from dpdk-next-net-intel.
Regards.
Qi
prev parent reply other threads:[~2019-02-28 2:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 18:13 Paul M Stillwell Jr
2019-02-18 12:46 ` Zhang, Qi Z
2019-02-28 2:04 ` Zhang, Qi Z [this message]
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=039ED4275CED7440929022BC67E7061153344FEE@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=paul.m.stillwell.jr@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).