Netdev List
 help / color / mirror / Atom feed
From: Thomas Falcon <tlfalcon@linux.vnet.ibm.com>
To: netdev@vger.kernel.org
Cc: jallen@linux.vnet.ibm.com, nfont@linux.vnet.ibm.com, davem@davemloft.net
Subject: Re: [PATCH net-next v3 0/7] ibmvnic: Update TX pool and TX routines
Date: Thu, 15 Mar 2018 19:48:36 -0500	[thread overview]
Message-ID: <6d96003e-5806-e62e-f383-d00992278655@linux.vnet.ibm.com> (raw)
In-Reply-To: <1521129763-21030-1-git-send-email-tlfalcon@linux.vnet.ibm.com>

On 03/15/2018 11:02 AM, Thomas Falcon wrote:
> This patch restructures the TX pool data structure and provides a
> separate TX pool array for TSO transmissions. This is already used
> in some way due to our unique DMA situation, namely that we cannot
> use single DMA mappings for packet data. Previously, both buffer
> arrays used the same pool entry. This restructuring allows for
> some additional cleanup in the driver code, especially in some
> places in the device transmit routine.
>
> In addition, it allows us to more easily track the consumer
> and producer indexes of a particular pool. This has been
> further improved by better tracking of in-use buffers to
> prevent possible data corruption in case an invalid buffer
> entry is used.
>
> v3: Forgot to update TX pool cleaning function to handle new data
> structures. Included 7th patch for that.
>
> v2: Fix typo in 3/6 commit subject line
>
> Thomas Falcon (7):
>   ibmvnic: Generalize TX pool structure
>   ibmvnic: Update and clean up reset TX pool routine
>   ibmvnic: Update release TX pool routine
>   ibmvnic: Update TX pool initialization routine
>   ibmvnic: Update TX and TX completion routines
>   ibmvnic: Improve TX buffer accounting
>   ibmvnic: Update TX pool cleaning routine
>
>  drivers/net/ethernet/ibm/ibmvnic.c | 275 +++++++++++++++++++++----------------
>  drivers/net/ethernet/ibm/ibmvnic.h |   8 +-
>  2 files changed, 160 insertions(+), 123 deletions(-)
>
Sorry again, I need to send another version because of a bug in the 7th patch.

      parent reply	other threads:[~2018-03-16  0:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 16:02 [PATCH net-next v3 0/7] ibmvnic: Update TX pool and TX routines Thomas Falcon
2018-03-15 16:02 ` [PATCH net-next v3 1/7] ibmvnic: Generalize TX pool structure Thomas Falcon
2018-03-16 16:52   ` David Miller
2018-03-16 18:15     ` Thomas Falcon
2018-03-15 16:02 ` [PATCH net-next v3 2/7] ibmvnic: Update and clean up reset TX pool routine Thomas Falcon
2018-03-15 16:02 ` [PATCH net-next v3 3/7] ibmvnic: Update release " Thomas Falcon
2018-03-15 16:02 ` [PATCH net-next v3 4/7] ibmvnic: Update TX pool initialization routine Thomas Falcon
2018-03-15 16:02 ` [PATCH net-next v3 5/7] ibmvnic: Update TX and TX completion routines Thomas Falcon
2018-03-15 16:02 ` [PATCH net-next v3 6/7] ibmvnic: Improve TX buffer accounting Thomas Falcon
2018-03-15 16:02 ` [PATCH net-next v3 7/7] ibmvnic: Update TX pool cleaning routine Thomas Falcon
2018-03-16  0:48 ` Thomas Falcon [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=6d96003e-5806-e62e-f383-d00992278655@linux.vnet.ibm.com \
    --to=tlfalcon@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=jallen@linux.vnet.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=nfont@linux.vnet.ibm.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