From: David Laight <david.laight.linux@gmail.com>
To: arthur@arthurfabre.com
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
jakub@cloudflare.com, hawk@kernel.org, yan@cloudflare.com,
jbrandeburg@cloudflare.com, thoiland@redhat.com,
lbiancon@redhat.com, Arthur Fabre <afabre@cloudflare.com>
Subject: Re: [PATCH RFC bpf-next 05/20] trait: Replace memcpy calls with inline copies
Date: Mon, 10 Mar 2025 22:15:48 +0000 [thread overview]
Message-ID: <20250310221548.1c198a2b@pumpkin> (raw)
In-Reply-To: <20250305-afabre-traits-010-rfc2-v1-5-d0ecfb869797@cloudflare.com>
On Wed, 05 Mar 2025 15:32:02 +0100
arthur@arthurfabre.com wrote:
> From: Arthur Fabre <afabre@cloudflare.com>
>
> When copying trait values to or from the caller, the size isn't a
> constant so memcpy() ends up being a function call.
>
> Replace it with an inline implementation that only handles the sizes we
> support.
>
> We store values "packed", so they won't necessarily be 4 or 8 byte
> aligned.
>
> Setting and getting traits is roughly ~40% faster.
>
> Signed-off-by: Arthur Fabre <afabre@cloudflare.com>
> ---
> include/net/trait.h | 25 +++++++++++++++++++------
> 1 file changed, 19 insertions(+), 6 deletions(-)
>
> diff --git a/include/net/trait.h b/include/net/trait.h
> index 536b8a17dbbc091b4d1a4d7b4b21c1e36adea86a..d4581a877bd57a32e2ad032147c906764d6d37f8 100644
> --- a/include/net/trait.h
> +++ b/include/net/trait.h
> @@ -7,6 +7,7 @@
> #include <linux/errno.h>
> #include <linux/string.h>
> #include <linux/bitops.h>
> +#include <linux/unaligned.h>
>
> /* Traits are a very limited KV store, with:
> * - 64 keys (0-63).
> @@ -145,23 +146,23 @@ int trait_set(void *traits, void *hard_end, u64 key, const void *val, u64 len, u
> memmove(traits + off + len, traits + off, traits_size(traits) - off);
> }
>
> - /* Set our value. */
> - memcpy(traits + off, val, len);
> -
> - /* Store our length in header. */
> u64 encode_len = 0;
> -
> switch (len) {
> case 2:
> + /* Values are least two bytes, so they'll be two byte aligned */
> + *(u16 *)(traits + off) = *(u16 *)val;
> encode_len = 1;
> break;
> case 4:
> + put_unaligned(*(u32 *)val, (u32 *)(traits + off));
> encode_len = 2;
> break;
> case 8:
> + put_unaligned(*(u64 *)val, (u64 *)(traits + off));
> encode_len = 3;
> break;
> }
> +
> h->high |= (encode_len >> 1) << key;
> h->low |= (encode_len & 1) << key;
> return 0;
> @@ -201,7 +202,19 @@ int trait_get(void *traits, u64 key, void *val, u64 val_len)
> if (real_len > val_len)
> return -ENOSPC;
>
> - memcpy(val, traits + off, real_len);
> + switch (real_len) {
> + case 2:
> + /* Values are least two bytes, so they'll be two byte aligned */
> + *(u16 *)val = *(u16 *)(traits + off);
> + break;
> + case 4:
> + *(u32 *)val = get_unaligned((u32 *)(traits + off));
> + break;
> + case 8:
> + *(u64 *)val = get_unaligned((u64 *)(traits + off));
> + break;
Should there be a 'default' in here?
Possibly just 'return 0'?
> + }
> +
> return real_len;
> }
>
>
next prev parent reply other threads:[~2025-03-10 22:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 14:31 [PATCH RFC bpf-next 00/20] traits: Per packet metadata KV store arthur
2025-03-05 14:31 ` [PATCH RFC bpf-next 01/20] trait: limited KV store for packet metadata arthur
2025-03-07 6:36 ` Alexei Starovoitov
2025-03-07 11:14 ` Arthur Fabre
2025-03-07 17:29 ` Alexei Starovoitov
2025-03-10 14:45 ` Arthur Fabre
2025-03-07 19:24 ` Jakub Sitnicki
2025-03-05 14:31 ` [PATCH RFC bpf-next 02/20] trait: XDP support arthur
2025-03-07 19:13 ` Lorenzo Bianconi
2025-03-10 15:50 ` Arthur Fabre
2025-03-05 14:32 ` [PATCH RFC bpf-next 03/20] trait: basic XDP selftest arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 04/20] trait: basic XDP benchmark arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 05/20] trait: Replace memcpy calls with inline copies arthur
2025-03-10 10:50 ` Lorenzo Bianconi
2025-03-10 15:52 ` Arthur Fabre
2025-03-10 22:15 ` David Laight [this message]
2025-03-05 14:32 ` [PATCH RFC bpf-next 06/20] trait: Replace memmove calls with inline move arthur
2025-03-06 10:14 ` Jesper Dangaard Brouer
2025-03-05 14:32 ` [PATCH RFC bpf-next 07/20] xdp: Track if metadata is supported in xdp_frame <> xdp_buff conversions arthur
2025-03-05 15:24 ` Alexander Lobakin
2025-03-05 17:02 ` Arthur Fabre
2025-03-06 11:12 ` Jesper Dangaard Brouer
2025-03-10 11:10 ` Lorenzo Bianconi
2025-03-05 14:32 ` [PATCH RFC bpf-next 08/20] trait: Propagate presence of traits to sk_buff arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 09/20] bnxt: Propagate trait presence to skb arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 10/20] ice: " arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 11/20] veth: " arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 12/20] virtio_net: " arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 13/20] mlx5: move xdp_buff scope one level up arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 14/20] mlx5: Propagate trait presence to skb arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 15/20] xdp generic: " arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 16/20] trait: Support sk_buffs arthur
2025-03-10 11:45 ` Lorenzo Bianconi
2025-03-05 14:32 ` [PATCH RFC bpf-next 17/20] trait: Allow socket filters to access traits arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 18/20] trait: registration API arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 19/20] trait: Sync linux/bpf.h to tools/ for trait registration arthur
2025-03-05 14:32 ` [PATCH RFC bpf-next 20/20] trait: register traits in benchmarks and tests arthur
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=20250310221548.1c198a2b@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=afabre@cloudflare.com \
--cc=arthur@arthurfabre.com \
--cc=bpf@vger.kernel.org \
--cc=hawk@kernel.org \
--cc=jakub@cloudflare.com \
--cc=jbrandeburg@cloudflare.com \
--cc=lbiancon@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=thoiland@redhat.com \
--cc=yan@cloudflare.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).