All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Joe Stringer <joe@isovalent.com>, bpf@vger.kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	ast@kernel.org, corbet@lwn.net, martin.lau@linux.dev,
	bagasdotme@gmail.com, maxtram95@gmail.com,
	john.fastabend@gmail.com
Subject: RE: [PATCH bpf-next v5 1/2] docs/bpf: Add table to describe LRU properties
Date: Sun, 23 Apr 2023 07:26:13 -0700	[thread overview]
Message-ID: <644540052bcaa_19af020828@john.notmuch> (raw)
In-Reply-To: <20230422172054.3355436-1-joe@isovalent.com>

Joe Stringer wrote:
> Depending on the map type and flags for LRU, different properties are
> global or percpu. Add a table to describe these.
> 
> Signed-off-by: Joe Stringer <joe@isovalent.com>
> ---
> v5: Use bold rather than verbatim for column header
> v4: Initial posting
> ---
>  Documentation/bpf/map_hash.rst | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/bpf/map_hash.rst b/Documentation/bpf/map_hash.rst
> index 8669426264c6..1314dfc5e7e1 100644
> --- a/Documentation/bpf/map_hash.rst
> +++ b/Documentation/bpf/map_hash.rst
> @@ -29,7 +29,16 @@ will automatically evict the least recently used entries when the hash
>  table reaches capacity. An LRU hash maintains an internal LRU list that
>  is used to select elements for eviction. This internal LRU list is
>  shared across CPUs but it is possible to request a per CPU LRU list with
> -the ``BPF_F_NO_COMMON_LRU`` flag when calling ``bpf_map_create``.
> +the ``BPF_F_NO_COMMON_LRU`` flag when calling ``bpf_map_create``.  The
> +following table outlines the properties of LRU maps depending on the a
> +map type and the flags used to create the map.
> +
> +======================== ========================= ================================
> +Flag                     ``BPF_MAP_TYPE_LRU_HASH`` ``BPF_MAP_TYPE_LRU_PERCPU_HASH``
> +======================== ========================= ================================
> +**BPF_F_NO_COMMON_LRU**  Per-CPU LRU, global map   Per-CPU LRU, per-cpu map
> +**!BPF_F_NO_COMMON_LRU** Global LRU, global map    Global LRU, per-cpu map
> +======================== ========================= ================================
>  
>  Usage
>  =====
> -- 
> 2.34.1
> 

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

  parent reply	other threads:[~2023-04-23 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-22 17:20 [PATCH bpf-next v5 1/2] docs/bpf: Add table to describe LRU properties Joe Stringer
2023-04-22 17:20 ` [PATCH bpf-next v5 2/2] docs/bpf: Add LRU internals description and graph Joe Stringer
2023-04-23 14:26   ` John Fastabend
2023-04-23 14:26 ` John Fastabend [this message]
2023-04-27 12:30 ` [PATCH bpf-next v5 1/2] docs/bpf: Add table to describe LRU properties patchwork-bot+netdevbpf

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=644540052bcaa_19af020828@john.notmuch \
    --to=john.fastabend@gmail.com \
    --cc=ast@kernel.org \
    --cc=bagasdotme@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=joe@isovalent.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=maxtram95@gmail.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.