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 2/2] docs/bpf: Add LRU internals description and graph
Date: Sun, 23 Apr 2023 07:26:35 -0700 [thread overview]
Message-ID: <6445401b297a1_19af02083@john.notmuch> (raw)
In-Reply-To: <20230422172054.3355436-2-joe@isovalent.com>
Joe Stringer wrote:
> Extend the bpf hashmap docs to include a brief description of the
> internals of the LRU map type (setting appropriate API expectations),
> including the original commit message from Martin and a variant on the
> graph that I had presented during my Linux Plumbers Conference 2022 talk
> on "Pressure feedback for LRU map types"[0].
>
> The node names in the dot file correspond roughly to the functions where
> the logic for those decisions or steps is defined, to help curious
> developers to cross-reference and update this logic if the details of
> the LRU implementation ever differ from this description.
>
> [0]: https://lpc.events/event/16/contributions/1368/
>
> Signed-off-by: Joe Stringer <joe@isovalent.com>
> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev 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 [this message]
2023-04-23 14:26 ` [PATCH bpf-next v5 1/2] docs/bpf: Add table to describe LRU properties John Fastabend
2023-04-27 12:30 ` 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=6445401b297a1_19af02083@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.