From: Hongru Zhang <zhanghongru06@gmail.com>
To: paul@paul-moore.com
Cc: linux-kernel@vger.kernel.org, omosnace@redhat.com,
selinux@vger.kernel.org, stephen.smalley.work@gmail.com,
zhanghongru06@gmail.com, zhanghongru@xiaomi.com
Subject: Re: [PATCH v3 1/2] selinux: Make avc cache slot size configurable during boot
Date: Wed, 22 Oct 2025 10:49:06 +0800 [thread overview]
Message-ID: <20251022024906.87974-1-zhanghongru@xiaomi.com> (raw)
In-Reply-To: <CAHC9VhQeW7fFtB5uGRJhU7882MsSLazHmOZ0UKj=pX6PKiwz8A@mail.gmail.com>
> That seems reasonable. I'm sure you've seen it already, but you'll
> likely need to modify AVC_DEF_CACHE_THRESHOLD as well ... or honestly
> just remove it in favor of AVC_CACHE_SLOTS, it's only used to set an
> initial value for the cache threshold.
How about this?
#define AVC_DEF_CACHE_THRESHOLD AVC_CACHE_SLOTS
We can preserve the original semantics this way.
>
> > I will try to submit the final version in Q1 2026 based on the discussion
> > (Because I have some planned Q4 work that hasn't been completed yet).
>
> No worries, thank you!
next prev parent reply other threads:[~2025-10-22 2:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 6:23 [PATCH v3 0/2] selinux: speed up avc_search_node() with large number of avc nodes Hongru Zhang
2025-09-26 6:23 ` [PATCH v3 1/2] selinux: Make avc cache slot size configurable during boot Hongru Zhang
2025-09-26 12:19 ` Stephen Smalley
2025-10-16 21:18 ` Paul Moore
2025-10-17 8:10 ` Hongru Zhang
2025-10-20 19:12 ` Paul Moore
2025-10-21 12:38 ` Hongru Zhang
2025-10-21 15:44 ` Paul Moore
2025-10-22 2:49 ` Hongru Zhang [this message]
2025-10-17 11:59 ` Stephen Smalley
2025-10-20 19:22 ` Paul Moore
2025-09-26 6:23 ` [PATCH v3 2/2] selinux: improve bucket distribution uniformity of avc_hash() Hongru Zhang
2025-09-26 12:26 ` Stephen Smalley
2025-10-16 21:18 ` Paul Moore
2025-10-17 9:53 ` Hongru Zhang
2025-10-20 19:44 ` Paul Moore
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=20251022024906.87974-1-zhanghongru@xiaomi.com \
--to=zhanghongru06@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=zhanghongru@xiaomi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®