All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Karlsson <magnus.karlsson@gmail.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	"Karlsson, Magnus" <magnus.karlsson@intel.com>
Subject: Re: [PATCH bpf-next 1/4] selftests: xsk: avoid bpf_link probe for existing xsk
Date: Thu, 30 Jun 2022 11:57:00 +0200	[thread overview]
Message-ID: <CAJ8uoz1Eo2Lsh0Gu4HED4cr7Ocqsd7=OjAf7wOrnvQ_tMa4Jgw@mail.gmail.com> (raw)
In-Reply-To: <20220629143458.934337-2-maciej.fijalkowski@intel.com>

On Wed, Jun 29, 2022 at 4:38 PM Maciej Fijalkowski
<maciej.fijalkowski@intel.com> wrote:
>
> Currently bpf_link probe is done for each call of xsk_socket__create().
> For cases where xsk context was previously created and current socket
> creation uses it, has_bpf_link will be overwritten, where it has already
> been initialized.
>
> Optimize this by moving the query to the xsk_create_ctx() so that when
> xsk_get_ctx() finds a ctx then no further bpf_link probes are needed.

This would be a good optimization to libxdp too.

Acked-by: Magnus Karlsson <magnus.karlsson@intel.com>

> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> ---
>  tools/testing/selftests/bpf/xsk.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/bpf/xsk.c b/tools/testing/selftests/bpf/xsk.c
> index eb50c3f336f8..fa13d2c44517 100644
> --- a/tools/testing/selftests/bpf/xsk.c
> +++ b/tools/testing/selftests/bpf/xsk.c
> @@ -958,6 +958,7 @@ static struct xsk_ctx *xsk_create_ctx(struct xsk_socket *xsk,
>         ctx->fill = fill;
>         ctx->comp = comp;
>         list_add(&ctx->list, &umem->ctx_list);
> +       ctx->has_bpf_link = xsk_probe_bpf_link();
>         return ctx;
>  }
>
> @@ -1059,7 +1060,6 @@ int xsk_socket__create_shared(struct xsk_socket **xsk_ptr,
>                 }
>         }
>         xsk->ctx = ctx;
> -       xsk->ctx->has_bpf_link = xsk_probe_bpf_link();
>
>         if (rx && !rx_setup_done) {
>                 err = setsockopt(xsk->fd, SOL_XDP, XDP_RX_RING,
> --
> 2.27.0
>

  reply	other threads:[~2022-06-30  9:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-29 14:34 [PATCH bpf-next 0/4] selftests: xsk: fix TEST_MODE_SKB in xdpxceiver Maciej Fijalkowski
2022-06-29 14:34 ` [PATCH bpf-next 1/4] selftests: xsk: avoid bpf_link probe for existing xsk Maciej Fijalkowski
2022-06-30  9:57   ` Magnus Karlsson [this message]
2022-06-29 14:34 ` [PATCH bpf-next 2/4] selftests: xsk: introduce XDP prog load based on existing AF_XDP socket Maciej Fijalkowski
2022-06-30  9:57   ` Magnus Karlsson
2022-06-29 14:34 ` [PATCH bpf-next 3/4] selftests: xsk: verify correctness of XDP prog attach point Maciej Fijalkowski
2022-06-30  9:57   ` Magnus Karlsson
2022-06-29 14:34 ` [PATCH bpf-next 4/4] selftests: xsk: destroy BPF resources only when ctx refcount drops to 0 Maciej Fijalkowski
2022-06-30  9:58   ` Magnus Karlsson
2022-06-30 20:52     ` Daniel Borkmann

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='CAJ8uoz1Eo2Lsh0Gu4HED4cr7Ocqsd7=OjAf7wOrnvQ_tMa4Jgw@mail.gmail.com' \
    --to=magnus.karlsson@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=maciej.fijalkowski@intel.com \
    --cc=magnus.karlsson@intel.com \
    --cc=netdev@vger.kernel.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.