netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: sdf@google.com
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
	"Daniel Borkmann" <daniel@iogearbox.net>,
	"Andrii Nakryiko" <andrii@kernel.org>,
	"Martin KaFai Lau" <martin.lau@linux.dev>,
	"Song Liu" <song@kernel.org>, "Yonghong Song" <yhs@fb.com>,
	"John Fastabend" <john.fastabend@gmail.com>,
	"KP Singh" <kpsingh@kernel.org>, "Hao Luo" <haoluo@google.com>,
	"Jiri Olsa" <jolsa@kernel.org>,
	"David S. Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Jesper Dangaard Brouer" <hawk@kernel.org>,
	"Björn Töpel" <bjorn@kernel.org>,
	"Magnus Karlsson" <magnus.karlsson@intel.com>,
	"Maciej Fijalkowski" <maciej.fijalkowski@intel.com>,
	"Jonathan Lemon" <jonathan.lemon@gmail.com>,
	bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/3] A couple of small refactorings of BPF program call sites
Date: Thu, 18 Aug 2022 15:26:46 -0700	[thread overview]
Message-ID: <Yv68pgkL++uD0a6e@google.com> (raw)
In-Reply-To: <20220818165906.64450-1-toke@redhat.com>

On 08/18, Toke H�iland-J�rgensen wrote:
> Stanislav suggested[0] that these small refactorings could be split out  
> from the
> XDP queueing RFC series and merged separately. The first change is a small
> repacking of struct softnet_data, the others change the BPF call sites to
> support full 64-bit values as arguments to bpf_redirect_map() and as the  
> return
> value of a BPF program, relying on the fact that BPF registers are always  
> 64-bit
> wide to maintain backwards compatibility.

> Please see the individual patches for details.

> [0]  
> https://lore.kernel.org/r/CAKH8qBtdnku7StcQ-SamadvAF==DRuLLZO94yOR1WJ9Bg=uX1w@mail.gmail.com

Looks like a nice cleanup to me:
Reviewed-by: Stanislav Fomichev <sdf@google.com>

Can you share more on this comment?

/* For some architectures, we need to do modulus in 32-bit width */

Some - which ones? And why do they need it to be 32-bit?

> Kumar Kartikeya Dwivedi (1):
>    bpf: Use 64-bit return value for bpf_prog_run

> Toke H�iland-J�rgensen (2):
>    dev: Move received_rps counter next to RPS members in softnet data
>    bpf: Expand map key argument of bpf_redirect_map to u64

>   include/linux/bpf-cgroup.h | 12 +++++-----
>   include/linux/bpf.h        | 16 ++++++-------
>   include/linux/filter.h     | 46 +++++++++++++++++++-------------------
>   include/linux/netdevice.h  |  2 +-
>   include/uapi/linux/bpf.h   |  2 +-
>   kernel/bpf/cgroup.c        | 12 +++++-----
>   kernel/bpf/core.c          | 14 ++++++------
>   kernel/bpf/cpumap.c        |  4 ++--
>   kernel/bpf/devmap.c        |  4 ++--
>   kernel/bpf/offload.c       |  4 ++--
>   kernel/bpf/verifier.c      |  2 +-
>   net/bpf/test_run.c         | 21 +++++++++--------
>   net/core/filter.c          |  4 ++--
>   net/packet/af_packet.c     |  7 ++++--
>   net/xdp/xskmap.c           |  4 ++--
>   15 files changed, 80 insertions(+), 74 deletions(-)

> --
> 2.37.2


  parent reply	other threads:[~2022-08-18 22:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 16:59 [PATCH bpf-next 0/3] A couple of small refactorings of BPF program call sites Toke Høiland-Jørgensen
2022-08-18 16:59 ` [PATCH bpf-next 1/3] dev: Move received_rps counter next to RPS members in softnet data Toke Høiland-Jørgensen
2022-08-19  3:01   ` Jakub Kicinski
2022-08-19 12:38     ` Toke Høiland-Jørgensen
2022-08-19 22:54       ` Jakub Kicinski
2022-08-22 10:17         ` Toke Høiland-Jørgensen
2022-08-18 16:59 ` [PATCH bpf-next 2/3] bpf: Expand map key argument of bpf_redirect_map to u64 Toke Høiland-Jørgensen
2022-08-18 16:59 ` [PATCH bpf-next 3/3] bpf: Use 64-bit return value for bpf_prog_run Toke Høiland-Jørgensen
2022-08-18 22:26 ` sdf [this message]
2022-08-19  5:24   ` [PATCH bpf-next 0/3] A couple of small refactorings of BPF program call sites Kumar Kartikeya Dwivedi
2022-08-23 22:29 ` Daniel Borkmann
2022-08-25 13:15   ` Kumar Kartikeya Dwivedi

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=Yv68pgkL++uD0a6e@google.com \
    --to=sdf@google.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bjorn@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=jonathan.lemon@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=martin.lau@linux.dev \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=song@kernel.org \
    --cc=toke@redhat.com \
    --cc=yhs@fb.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).