From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [RFC PATCH 0/8] remove use of rte_memcpy from net/intel
Date: Tue, 19 May 2026 12:43:32 -0700 [thread overview]
Message-ID: <20260519124332.5e68fd8f@phoenix.local> (raw)
In-Reply-To: <20260519160823.1004973-1-bruce.richardson@intel.com>
On Tue, 19 May 2026 16:05:57 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:
> This RFC proposed to replace all instances of rte_memcpy in Intel
> (and former-Intel) net drivers with just regular memcpy. This is
> done on the basis that the memcpy use is not datapath, but is used
> for flow configuration, virt-channel (to firmware or PF) messaging
> and other control path functions.
Makes sense. You might also want to look for where structure
assignment can be used instead of memcpy. Keeping data types
is a good thing.
next prev parent reply other threads:[~2026-05-19 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 16:05 [RFC PATCH 0/8] remove use of rte_memcpy from net/intel Bruce Richardson
2026-05-19 16:05 ` [RFC PATCH 1/8] net/ice: replace use of DPDK-specific memcpy function Bruce Richardson
2026-05-19 16:05 ` [RFC PATCH 2/8] net/iavf: " Bruce Richardson
2026-05-19 16:06 ` [RFC PATCH 3/8] net/i40e: " Bruce Richardson
2026-05-19 16:06 ` [RFC PATCH 4/8] net/ixgbe: " Bruce Richardson
2026-05-19 16:06 ` [RFC PATCH 5/8] net/e1000: " Bruce Richardson
2026-05-19 16:06 ` [RFC PATCH 6/8] net/idpf: " Bruce Richardson
2026-05-19 16:06 ` [RFC PATCH 7/8] net/cpfl: " Bruce Richardson
2026-05-19 16:06 ` [RFC PATCH 8/8] net/ipn3ke: " Bruce Richardson
2026-05-19 17:57 ` [RFC PATCH 0/8] remove use of rte_memcpy from net/intel Morten Brørup
2026-05-21 9:48 ` Bruce Richardson
2026-05-19 19:43 ` Stephen Hemminger [this message]
2026-05-20 7:44 ` Bruce Richardson
2026-05-20 13:50 ` Morten Brørup
2026-05-20 14:53 ` Bruce Richardson
2026-05-20 16:45 ` Stephen Hemminger
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=20260519124332.5e68fd8f@phoenix.local \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.