DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: jgrajcia@cisco.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/memif: replace memcpy() with rte_memcpy() to improve perf
Date: Wed, 23 Jun 2021 10:03:47 -0700	[thread overview]
Message-ID: <20210623100347.58f9a384@hermes.local> (raw)
In-Reply-To: <20210623164935.59796-1-drc@linux.vnet.ibm.com>

On Wed, 23 Jun 2021 09:49:35 -0700
David Christensen <drc@linux.vnet.ibm.com> wrote:

> Replacing memcpy() with rte_memcpy() improved 64 byte packet
> performance by 33% on a POWER9 system and by 10% on an x86_64
> system.

I see rte_memcpy was already used in the patch diff

> Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
> ---
>  drivers/net/memif/rte_eth_memif.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/net/memif/rte_eth_memif.c b/drivers/net/memif/rte_eth_memif.c
> index d17222c612..330c9c2fd6 100644
> --- a/drivers/net/memif/rte_eth_memif.c
> +++ b/drivers/net/memif/rte_eth_memif.c
> @@ -384,8 +384,8 @@ eth_memif_rx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
>  				rte_pktmbuf_pkt_len(mbuf_head) += cp_len;
>  
>  			rte_memcpy(rte_pktmbuf_mtod_offset(mbuf, void *, dst_off),
> -			       (uint8_t *)memif_get_buffer(proc_private, d0) + src_off,
> -			       cp_len);
> +			       (uint8_t *)memif_get_buffer(proc_private, d0)
> +			       + src_off, cp_len);

This just changes line break for no good reason.
>  
>  			src_off += cp_len;
>  			dst_off += cp_len;
> @@ -644,7 +644,8 @@ eth_memif_tx(void *queue, struct rte_mbuf **bufs, uint16_t nb_pkts)
>  			}
>  			cp_len = RTE_MIN(dst_len, src_len);
>  
> -			rte_memcpy((uint8_t *)memif_get_buffer(proc_private, d0) + dst_off,
> +			rte_memcpy((uint8_t *)
> +			       memif_get_buffer(proc_private, d0) + dst_off,
>  			       rte_pktmbuf_mtod_offset(mbuf, void *, src_off),
>  			       cp_len);
>  

ditto.

Look like this patch is confused, the description does not match the code.

  reply	other threads:[~2021-06-23 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 16:49 David Christensen
2021-06-23 17:03 ` Stephen Hemminger [this message]
2021-07-01 16:22   ` Andrew Rybchenko
2021-06-23 20:31 ` David Christensen
2021-06-24 16:15   ` Tyler Retzlaff
2021-07-01 16:19     ` Andrew Rybchenko

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=20210623100347.58f9a384@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=jgrajcia@cisco.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).