From: Greg KH <greg@kroah.com>
To: Gerrit Huizenga <gh@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org,
Rik van Riel <riel@redhat.com>, Chris Mason <mason@suse.com>,
ckrm-tech <ckrm-tech@lists.sourceforge.net>
Subject: Re: [PATCH] CKRM: 5/10 CKRM: Task based management for CPU, memory and Disk I/O.
Date: Mon, 29 Nov 2004 14:23:23 -0800 [thread overview]
Message-ID: <20041129222323.GE19892@kroah.com> (raw)
In-Reply-To: <E1CYqaE-00058c-00@w-gerrit.beaverton.ibm.com>
On Mon, Nov 29, 2004 at 10:49:09AM -0800, Gerrit Huizenga wrote:
> +#define TC_DEBUG(fmt, args...) do { \
> +/* printk("%s: " fmt, __FUNCTION__ , ## args); */ } while (0)
Again with the new debug macro :(
> +static struct ckrm_task_class taskclass_dflt_class = {
> +};
Empty structure? Why?
> +// Hubertus .. following functions should move to ckrm_rc.h
Why haven't they moved :)
> +static inline void ckrm_task_lock(struct task_struct *tsk)
> +{
> + spin_lock(&tsk->ckrm_tsklock);
> +}
Just lock (or unlock) the lock, don't wrap a lock in a function.
> +DECLARE_MUTEX(async_serializer); // serialize all async functions
Should this really be global? The code says otherwise :)
> + printk("...... Initializing ClassType<%s> ........\n",
> + CT_taskclass.name);
What a pretty log message. Unfortunately it's wrong (me hears the
growing mumblings of the kernel janitor mob...)
> +#if 0
> +
> +/******************************************************************************
> + * Debugging Task Classes: Utility functions
> + ******************************************************************************/
Then remove the code, if it's not needed.
> +EXPORT_SYMBOL(tcp_v4_lookup_listener);
Not EXPORT_SYMBOL_GPL()?
thanks,
greg k-h
next prev parent reply other threads:[~2004-11-29 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:49 Gerrit Huizenga
2004-11-29 22:23 ` Greg KH [this message]
2005-02-24 9:33 ` Gerrit Huizenga
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=20041129222323.GE19892@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=gh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=riel@redhat.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
Powered by JetHome