Netdev List
 help / color / mirror / Atom feed
From: Dalon L Westergreen <dalon.westergreen@linux.intel.com>
To: Atsushi Nemoto <atsushi.nemoto@sord.co.jp>
Cc: thor.thayer@linux.intel.com, netdev@vger.kernel.org,
	tomonori.sakita@sord.co.jp
Subject: Re: [PATCH] net: altera_tse: fix msgdma_tx_completion on non-zero fill_level case
Date: Thu, 24 Jan 2019 06:57:25 -0800	[thread overview]
Message-ID: <e23d68abafd5d852b9b84c7dea1ae33521ac8da4.camel@linux.intel.com> (raw)
In-Reply-To: <20190124.140544.1043020473181933407.atsushi.nemoto@sord.co.jp>

On Thu, 2019-01-24 at 14:05 +0900, Atsushi Nemoto wrote:
> On Wed, 23 Jan 2019 14:47:06 -0800, Dalon L Westergreen <
> dalon.westergreen@linux.intel.com> wrote:
> > > >   	if (inuse) { /* Tx FIFO is not empty */
> > > > -		ready = priv->tx_prod - priv->tx_cons - inuse - 1;
> > > > +		ready = priv->tx_prod - priv->tx_cons - inuse;
> > dont think my last email went through..
> > 
> > I am not sure about this.  This register indicates the number of entries
> > still to be processed by the dma.  the -1 is intended to represent the
> > decriptor currently being processed.  If ready is 
> > priv->tx_prod - priv->tx_cons - inuse couldn't you end up processing 1
> > too many packets?  IE: ready is 1 greater then the actual completed
> > packets?
> > 
> > I do agree that we should not be returning a negative value, but i dont
> > think i agree removing the -1 is the answer.  perhaps just check that ready
> > is greater than 0?
> 
> Thank you for review.
> 
> I agree with you.  It would be OK returning a possibly off-by-one
> value unless it is not an negative value.
> 
> Then, how about this instead?
> 

This works for me. thanks.

> --- a/drivers/net/ethernet/altera/altera_msgdma.c
> +++ b/drivers/net/ethernet/altera/altera_msgdma.c
> @@ -145,7 +145,8 @@ u32 msgdma_tx_completions(struct altera_tse_private *priv)
>  			& 0xffff;
>  
>  	if (inuse) { /* Tx FIFO is not empty */
> -		ready = priv->tx_prod - priv->tx_cons - inuse - 1;
> +		ready = max_t(int,
> +			      priv->tx_prod - priv->tx_cons - inuse - 1, 0);
>  	} else {
>  		/* Check for buffered last packet */
>  		status = csrrd32(priv->tx_dma_csr, msgdma_csroffs(status));


      reply	other threads:[~2019-01-24 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  8:29 [PATCH] net: altera_tse: fix msgdma_tx_completion on non-zero fill_level case Atsushi Nemoto
2019-01-22 17:20 ` Thor Thayer
2019-01-23 22:47   ` Dalon L Westergreen
2019-01-24  5:05     ` Atsushi Nemoto
2019-01-24 14:57       ` Dalon L Westergreen [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=e23d68abafd5d852b9b84c7dea1ae33521ac8da4.camel@linux.intel.com \
    --to=dalon.westergreen@linux.intel.com \
    --cc=atsushi.nemoto@sord.co.jp \
    --cc=netdev@vger.kernel.org \
    --cc=thor.thayer@linux.intel.com \
    --cc=tomonori.sakita@sord.co.jp \
    /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