From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
tglx@linutronix.de, arnd@arndb.de,
Matthew Wilcox <willy@infradead.org>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH v7 3/4] ipc: Allow boot time extension of IPCMNI from 32k to 2M
Date: Mon, 7 May 2018 23:17:04 +0000 [thread overview]
Message-ID: <20180507231704.GX27853@wotan.suse.de> (raw)
In-Reply-To: <1525726752-29281-4-git-send-email-longman@redhat.com>
On Mon, May 07, 2018 at 04:59:11PM -0400, Waiman Long wrote:
> diff --git a/ipc/ipc_sysctl.c b/ipc/ipc_sysctl.c
> index 49f9bf4..d62335f 100644
> --- a/ipc/ipc_sysctl.c
> +++ b/ipc/ipc_sysctl.c
> @@ -120,7 +120,8 @@ static int proc_ipc_sem_dointvec(struct ctl_table *table, int write,
> static int zero;
> static int one = 1;
> static int int_max = INT_MAX;
> -static int ipc_mni = IPCMNI;
> +int ipc_mni __read_mostly = IPCMNI;
> +int ipc_mni_shift __read_mostly = IPCMNI_SHIFT;
>
> static struct ctl_table ipc_kern_table[] = {
> {
Is use of ipc_mni and ipc_mni_shift a hot path? As per Christoph Lameter,
its use should be reserved for data that is actually used frequently in hot
paths, and typically this was done after performance traces reveal contention
because a neighboring variable was frequently written to [0]. These would also
be tightly packed, to reduce the number of cachelines needed to execute a
critical path, so we should be selective about what variables use it.
Your commit log does not describe why you'd use __read_mostly here. It would
be useful if it did.
[0] https://lkml.kernel.org/r/alpine.DEB.2.11.1504301343190.28879@gentwo.org
Luis
next prev parent reply other threads:[~2018-05-07 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 20:59 [PATCH v7 0/4] ipc: IPCMNI limit check for *mni & increase that limit Waiman Long
2018-05-07 20:59 ` [PATCH v7 1/4] ipc: IPCMNI limit check for msgmni and shmmni Waiman Long
2018-05-07 22:39 ` Luis R. Rodriguez
2018-05-07 23:57 ` Waiman Long
2018-05-09 19:32 ` Luis R. Rodriguez
2018-06-18 9:52 ` Waiman Long
2018-05-07 20:59 ` [PATCH v7 2/4] ipc: IPCMNI limit check for semmni Waiman Long
2018-05-07 20:59 ` [PATCH v7 3/4] ipc: Allow boot time extension of IPCMNI from 32k to 2M Waiman Long
2018-05-07 23:17 ` Luis R. Rodriguez [this message]
2018-05-08 0:04 ` Waiman Long
2018-05-07 20:59 ` [PATCH v7 4/4] ipc: Conserve sequence numbers in extended IPCMNI mode Waiman Long
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=20180507231704.GX27853@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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).