From: Randy Dunlap <randy.dunlap@oracle.com>
To: Nadia.Derbey@bull.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 5/6] per namespace tunables
Date: Wed, 24 Jan 2007 14:41:56 -0800 [thread overview]
Message-ID: <20070124144156.ff29d5dd.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070116063030.317602000@bull.net>
On Tue, 16 Jan 2007 07:15:21 +0100 Nadia.Derbey@bull.net wrote:
> [PATCH 05/06]
>
> This patch introduces all that is needed to process per namespace tunables.
>
> ---
> include/linux/akt.h | 12 +++++++
> kernel/autotune/akt.c | 80 ++++++++++++++++++++++++++++++++++++++------------
> 2 files changed, 73 insertions(+), 19 deletions(-)
>
> +/*
> + * FUNCTION: This routine gets the actual auto_tune structure for the
> + * tunables that are per namespace (presently only ipc ones).
> + *
> + * RETURN VALUE: pointer to the tunable structure for the current namespace
> + */
Please use kernel-doc format for function comment blocks.
(see Documentation/kernel-doc-nano-HOWTO.txt)
> +static struct auto_tune *get_ns_tunable(struct auto_tune *p)
> +{
> + if (p->flags & TUNABLE_IPC_NS) {
> + char *shift = (char *) p;
> + struct ipc_namespace *ns = current->nsproxy->ipc_ns;
> +
> + shift = (shift - (char *) &init_ipc_ns) + (char *) ns;
> +
> + return (struct auto_tune *) shift;
> + }
> +
> + return p;
> +}
> +
> +
> EXPORT_SYMBOL_GPL(register_tunable);
> EXPORT_SYMBOL_GPL(unregister_tunable);
and put EXPORT_SYMBOL/_GPL() immediately after each function
that is being exported.
---
~Randy
next prev parent reply other threads:[~2007-01-24 22:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 6:15 [RFC][PATCH 0/6] Automatice kernel tunables (AKT) Nadia.Derbey
2007-01-16 6:15 ` [RFC][PATCH 1/6] Tunable structure and registration routines Nadia.Derbey
2007-01-25 0:32 ` Randy Dunlap
2007-01-25 16:26 ` Nadia Derbey
2007-01-25 16:34 ` Randy Dunlap
2007-01-25 17:01 ` Nadia Derbey
2007-01-16 6:15 ` [RFC][PATCH 2/6] auto_tuning activation Nadia.Derbey
2007-01-16 6:15 ` [RFC][PATCH 3/6] tunables associated kobjects Nadia.Derbey
2007-01-16 6:15 ` [RFC][PATCH 4/6] min and max kobjects Nadia.Derbey
2007-01-24 22:41 ` Randy Dunlap
2007-01-25 16:34 ` Nadia Derbey
2007-01-16 6:15 ` [RFC][PATCH 5/6] per namespace tunables Nadia.Derbey
2007-01-24 22:41 ` Randy Dunlap [this message]
2007-01-16 6:15 ` [RFC][PATCH 6/6] automatic tuning applied to some kernel components Nadia.Derbey
2007-01-22 19:56 ` Andrew Morton
2007-01-23 14:40 ` Nadia Derbey
2007-02-07 21:18 ` Eric W. Biederman
2007-02-09 12:27 ` Nadia Derbey
2007-02-09 18:35 ` Eric W. Biederman
2007-02-13 9:06 ` Nadia Derbey
2007-02-13 10:10 ` Eric W. Biederman
2007-02-15 7:07 ` Nadia Derbey
2007-02-15 7:49 ` Eric W. Biederman
2007-02-15 8:25 ` Nadia Derbey
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=20070124144156.ff29d5dd.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Nadia.Derbey@bull.net \
--cc=linux-kernel@vger.kernel.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