From: Stephen Hemminger <stephen@networkplumber.org>
To: Kamil Vojanec <vojanec@cesnet.cz>
Cc: dev@dpdk.org, Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: Re: [RFC] table: report victim replace stats in LRU tables
Date: Fri, 11 Oct 2024 19:57:04 -0700 [thread overview]
Message-ID: <20241011195704.57afa017@hermes.local> (raw)
In-Reply-To: <20240819052330.46122-1-vojanec@cesnet.cz>
On Mon, 19 Aug 2024 07:23:30 +0200
Kamil Vojanec <vojanec@cesnet.cz> wrote:
> LRU caches replace records when requested table bucket is full. There
> is, however, no information about this happening in either the return
> value or the statistics. This commit introduces a counter for such
> cases.
>
> Signed-off-by: Kamil Vojanec <vojanec@cesnet.cz>
Good concept, but needs work. Lots of trivial checkpatch stuff and
fails testing on 32 bit ARM might be infrastructure issue.
next prev parent reply other threads:[~2024-10-12 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 11:58 Kamil Vojanec
2024-08-19 5:23 ` Kamil Vojanec
2024-10-12 2:57 ` Stephen Hemminger [this message]
2024-10-13 1:19 ` Stephen Hemminger
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=20241011195704.57afa017@hermes.local \
--to=stephen@networkplumber.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=vojanec@cesnet.cz \
/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).