All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Takshak Chahande <ctakshak@fb.com>,
	netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: andrii@kernel.org, ast@kernel.org, ctakshak@fb.com,
	ndixit@fb.com, kafai@fb.com, andriin@fb.com,
	daniel@iogearbox.net, yhs@fb.com, ctakshak@gmail.com
Subject: RE: [PATCH bpf-next v5 1/2] bpf: Extend batch operations for map-in-map bpf-maps
Date: Sun, 08 May 2022 20:23:56 -0700	[thread overview]
Message-ID: <6278894cd9ef6_6265d20832@john.notmuch> (raw)
In-Reply-To: <20220506010049.1980482-1-ctakshak@fb.com>

Takshak Chahande wrote:
> This patch extends batch operations support for map-in-map map-types:
> BPF_MAP_TYPE_HASH_OF_MAPS and BPF_MAP_TYPE_ARRAY_OF_MAPS
> 
> A usecase where outer HASH map holds hundred of VIP entries and its
> associated reuse-ports per VIP stored in REUSEPORT_SOCKARRAY type
> inner map, needs to do batch operation for performance gain.
> 
> This patch leverages the exiting generic functions for most of the batch
> operations. As map-in-map's value contains the actual reference of the inner map,
> for BPF_MAP_TYPE_HASH_OF_MAPS type, it needed an extra step to fetch the
> map_id from the reference value.
> 
> selftests are added in next patch 2/2.
> 
> Signed-off-by: Takshak Chahande <ctakshak@fb.com>
> Acked-by: Yonghong Song <yhs@fb.com>
> ---

Acked-by: John Fastabend <john.fastabend@gmail.com>

      parent reply	other threads:[~2022-05-09  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06  1:00 [PATCH bpf-next v5 1/2] bpf: Extend batch operations for map-in-map bpf-maps Takshak Chahande
2022-05-06  1:00 ` [PATCH bpf-next v5 2/2] selftests/bpf: handle " Takshak Chahande
2022-05-09  3:23 ` John Fastabend [this message]

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=6278894cd9ef6_6265d20832@john.notmuch \
    --to=john.fastabend@gmail.com \
    --cc=andrii@kernel.org \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=ctakshak@fb.com \
    --cc=ctakshak@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=kafai@fb.com \
    --cc=ndixit@fb.com \
    --cc=netdev@vger.kernel.org \
    --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 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.