qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Andrey Smirnov <andrew.smirnov@gmail.com>, qemu-ppc@nongnu.org
Cc: Scott Wood <scottwood@freescale.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] fsl_etsec: Fix Tx BD ring wrapping handling
Date: Fri, 6 Jan 2017 10:53:12 +0800	[thread overview]
Message-ID: <c42c0854-2c8c-9ae4-6d66-daff02a2a290@redhat.com> (raw)
In-Reply-To: <20170105202636.4003-1-andrew.smirnov@gmail.com>



On 2017年01月06日 04:26, Andrey Smirnov wrote:
> Current code that handles Tx buffer desciprtor ring scanning employs the
> following algorithm:
>
> 	1. Restore current buffer descriptor pointer from TBPTRn
>
> 	2. Process current descriptor
>
> 	3. If current descriptor has BD_WRAP flag set set current
> 	   descriptor pointer to start of the descriptor ring
>
> 	4. If current descriptor points to start of the ring exit the
> 	   loop, otherwise increment current descriptor pointer and go
> 	   to #2
>
> 	5. Store current descriptor in TBPTRn
>
> The way the code is implemented results in buffer descriptor ring being
> scanned starting at offset/descriptor #0. While covering 99% of the
> cases, this algorithm becomes problematic for a number of edge cases.
>
> Consider the following scenario: guest OS driver initializes descriptor
> ring to N individual descriptors and starts sending data out. Depending
> on the volume of traffic and probably guest OS driver implementation it
> is possible that an edge case where a packet, spread across 2
> descriptors is placed in descriptors N - 1 and 0 in that order(it is
> easy to imagine similar examples involving more than 2 descriptors).
>
> What happens then is aforementioned algorithm starts at descriptor 0,
> sees a descriptor marked as BD_LAST, which it happily sends out as a
> separate packet(very much malformed at this point) then the iteration
> continues and the first part of the original packet is tacked to the
> next transmission which ends up being bogus as well.
>
> This behvaiour can be pretty reliably observed when scp'ing data from a
> guest OS via TAP interface for files larger than 160K (every time for
> 700K+).
>
> This patch changes the scanning algorithm to do the following:
>
> 	1. Restore "current" buffer descriptor pointer from
> 	   TBPTRn
>
> 	2. If "current" descriptor does not have BD_TX_READY set, goto #6
>
> 	3. Process current descriptor
>
> 	4. If "current" descriptor has BD_WRAP flag set "current"
> 	   descriptor pointer to start of the descriptor ring otherwise
> 	   set increment "current" by the size of one descriptor
>
> 	5. Goto #1
>
> 	6. Save "current" buffer descriptor in TBPTRn
>
> This way we preserve the information about which descriptor was
> processed last and always start where we left off avoiding the original
> problem. On top of that, judging by the following excerpt from
> MPC8548ERM (p. 14-48):
>
> "... When the end of the TxBD ring is reached, eTSEC initializes TBPTRn
> to the value in the corresponding TBASEn. The TBPTR register is
> internally written by the eTSEC’s DMA controller during
> transmission. The pointer increments by eight (bytes) each time a
> descriptor is closed successfully by the eTSEC..."
>
> revised algorithm might also a more correct way of emulating this aspect
> of eTSEC peripheral.
>
> Cc: Alexander Graf <agraf@suse.de>
> Cc: Scott Wood <scottwood@freescale.com>
> Cc: Jason Wang <jasowang@redhat.com>
> Cc: qemu-devel@nongnu.org
> Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
> ---
>
> Changes since v1:
>
> 	- Simplified new algorithm as per Jason Wang's suggestion
>
> Changes since v2:
>
> 	- Fixed code style problems
>
>   hw/net/fsl_etsec/rings.c | 19 +++++++++----------
>   1 file changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/hw/net/fsl_etsec/rings.c b/hw/net/fsl_etsec/rings.c
> index 54c0127..d0f93ee 100644
> --- a/hw/net/fsl_etsec/rings.c
> +++ b/hw/net/fsl_etsec/rings.c
> @@ -358,25 +358,24 @@ void etsec_walk_tx_ring(eTSEC *etsec, int ring_nbr)
>           /* Save flags before BD update */
>           bd_flags = bd.flags;
>   
> -        if (bd_flags & BD_TX_READY) {
> -            process_tx_bd(etsec, &bd);
> -
> -            /* Write back BD after update */
> -            write_buffer_descriptor(etsec, bd_addr, &bd);
> +        if (!(bd_flags & BD_TX_READY)) {
> +            break;
>           }
>   
> +        process_tx_bd(etsec, &bd);
> +        /* Write back BD after update */
> +        write_buffer_descriptor(etsec, bd_addr, &bd);
> +
>           /* Wrap or next BD */
>           if (bd_flags & BD_WRAP) {
>               bd_addr = ring_base;
>           } else {
>               bd_addr += sizeof(eTSEC_rxtx_bd);
>           }
> +    } while (TRUE);
>   
> -    } while (bd_addr != ring_base);
> -
> -    bd_addr = ring_base;
> -
> -    /* Save the Buffer Descriptor Pointers to current bd */
> +    /* Save the Buffer Descriptor Pointers to last bd that was not
> +     * succesfully closed */
>       etsec->regs[TBPTR0 + ring_nbr].value = bd_addr;
>   
>       /* Set transmit halt THLTx */

Applied to -net.

Thanks

      reply	other threads:[~2017-01-06  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 20:26 [Qemu-devel] [PATCH v3] fsl_etsec: Fix Tx BD ring wrapping handling Andrey Smirnov
2017-01-06  2:53 ` Jason Wang [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=c42c0854-2c8c-9ae4-6d66-daff02a2a290@redhat.com \
    --to=jasowang@redhat.com \
    --cc=agraf@suse.de \
    --cc=andrew.smirnov@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=scottwood@freescale.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).