Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v1 0/4] ice: transmit improvement series
Date: Tue, 26 Oct 2021 16:21:42 +0000	[thread overview]
Message-ID: <7afd99cc66d66f81ce68e9bd9e9cc116cefab1eb.camel@intel.com> (raw)
In-Reply-To: <20211026000826.156803-1-jesse.brandeburg@intel.com>

On Mon, 2021-10-25 at 17:08 -0700, Jesse Brandeburg wrote:
> Modify the ice driver to make a few modest changes to the transmit
> hot path in order to reduce the number of cycles used, particularly
> with high intensity workloads such as pktgen or IP forwarding.
> 
> Several of these changes are just using simpler API calls in
> netdevice.h (welcome to 2015!)
> 
> The VSI_DOWN patch is a simple fix to make sure the driver's
> statements
> about holding certain state bits for functions is enforced and
> remains
> that way.
> 
> Jesse Brandeburg (4):
> ? ice: update to newer kernel API
> ? ice: use prefetch methods
> ? ice: tighter control over VSI_DOWN state
> ? ice: use modern kernel API for kick

It looks like patch 2 never made it to the list [1]. Seems like the
email issues may be further reaching than kernel.org.

Thanks,
Tony

[1] https://patchwork.ozlabs.org/project/intel-wired-
lan/list/?series=268871

> ?drivers/net/ethernet/intel/ice/ice_ethtool.c |? 6 ++-
> ?drivers/net/ethernet/intel/ice/ice_main.c??? |? 7 ++--
> ?drivers/net/ethernet/intel/ice/ice_txrx.c??? | 40 +++++++++++++-----
> --
> ?3 files changed, 34 insertions(+), 19 deletions(-)
> 


  parent reply	other threads:[~2021-10-26 16:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  0:08 [Intel-wired-lan] [PATCH net-next v1 0/4] ice: transmit improvement series Jesse Brandeburg
2021-10-26  0:08 ` [Intel-wired-lan] [PATCH net-next v1 1/4] ice: update to newer kernel API Jesse Brandeburg
2021-11-05  9:10   ` G, GurucharanX
2021-10-26  0:08 ` [Intel-wired-lan] [PATCH net-next v1 3/4] ice: tighter control over VSI_DOWN state Jesse Brandeburg
2021-11-05  9:10   ` G, GurucharanX
2021-10-26  0:08 ` [Intel-wired-lan] [PATCH net-next v1 4/4] ice: use modern kernel API for kick Jesse Brandeburg
2021-11-05  9:11   ` G, GurucharanX
2021-10-26 16:21 ` Nguyen, Anthony L [this message]
2021-10-27 19:46   ` [Intel-wired-lan] [PATCH net-next v1 0/4] ice: transmit improvement series Jesse Brandeburg

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=7afd99cc66d66f81ce68e9bd9e9cc116cefab1eb.camel@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@osuosl.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