public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
	<magnus.karlsson@intel.com>, <alasdair.mcwilliam@outlook.com>
Subject: Re: [PATCH v2 intel-net 0/2] ice: xsk: ZC changes
Date: Wed, 31 Aug 2022 13:11:30 -0700	[thread overview]
Message-ID: <148662c5-9be0-3872-fc66-e600163ca49f@intel.com> (raw)
In-Reply-To: <20220830125122.9665-1-maciej.fijalkowski@intel.com>



On 8/30/2022 5:51 AM, Maciej Fijalkowski wrote:
> Hi,
> 
> this set consists of two fixes to issues that were either pointed out on
> indirectly (John was reviewing AF_XDP selftests that were testing ice's
> ZC support) mailing list or were directly reported by customers.
> 
> First patch allows user space to see done descriptor in CQ even after a
> single frame being transmitted and second patch removes the need for
> having HW rings sized to power of 2 number of descriptors when used
> against AF_XDP.
> 
> I also forgot to mention that due to the current Tx cleaning algorithm,
> 4k HW ring was broken and these two patches bring it back to life, so we
> kill two birds with one stone.

Hi Maciej,

This isn't applying to net-queue.

Thanks,
Tony

      parent reply	other threads:[~2022-08-31 20:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 12:51 [PATCH v2 intel-net 0/2] ice: xsk: ZC changes Maciej Fijalkowski
2022-08-30 12:51 ` [PATCH v2 intel-net 1/2] ice: xsk: change batched Tx descriptor cleaning Maciej Fijalkowski
2022-08-31 20:14   ` Tony Nguyen
2022-08-30 12:51 ` [PATCH v2 intel-net 2/2] ice: xsk: drop power of 2 ring size restriction for AF_XDP Maciej Fijalkowski
2022-08-31 20:11 ` Tony Nguyen [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=148662c5-9be0-3872-fc66-e600163ca49f@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=alasdair.mcwilliam@outlook.com \
    --cc=bpf@vger.kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --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