From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Guillaume Thouvenin <guillaume.thouvenin@bull.net>
Cc: Alexander Nyberg <alexn@dsv.su.se>, Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>, Jay Lan <jlan@engr.sgi.com>,
aq <aquynh@gmail.com>, Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
elsa-devel <elsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2.6.12-rc3-mm3] connector: add a fork connector
Date: Mon, 09 May 2005 22:00:27 +1000 [thread overview]
Message-ID: <427F50DB.2020705@yahoo.com.au> (raw)
In-Reply-To: <1115638724.8540.59.camel@frecb000711.frec.bull.fr>
Guillaume Thouvenin wrote:
> On Mon, 2005-05-09 at 11:31 +0200, Alexander Nyberg wrote:
>>>Index: linux-2.6.12-rc3-mm3/kernel/fork.c
>>>===================================================================
>>>--- linux-2.6.12-rc3-mm3.orig/kernel/fork.c 2005-05-09 07:45:56.000000000 +0200
>>>+++ linux-2.6.12-rc3-mm3/kernel/fork.c 2005-05-09 08:03:15.000000000 +0200
>>>@@ -41,6 +41,7 @@
>>> #include <linux/profile.h>
>>> #include <linux/rmap.h>
>>> #include <linux/acct.h>
>>>+#include <linux/cn_fork.h>
>>>
>>> #include <asm/pgtable.h>
>>> #include <asm/pgalloc.h>
>>>@@ -63,6 +64,14 @@ DEFINE_PER_CPU(unsigned long, process_co
>>>
>>> EXPORT_SYMBOL(tasklist_lock);
>>>
>>>+#ifdef CONFIG_FORK_CONNECTOR
>>>+/*
>>>+ * fork_counts is used by the fork_connector() inline routine as
>>>+ * the sequence number of the netlink message.
>>>+ */
>>>+static DEFINE_PER_CPU(unsigned long, fork_counts);
>>>+#endif /* CONFIG_FORK_CONNECTOR */
>>>+
>>
>>The above should go into cn_fork.c
>
>
> I don't see why.
>
Because you get these ugly ifdefs and things just spilling into
conceptually the wrong place. Why should anyone apart from the
fork connecter care how `fork_counts` is stored? And why would
any generic code care that it is defined when CONFIG_FORK_CONNECTOR
is set? Alexander is right, unless I missed something that requires
reading the code :)
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2005-05-09 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 8:07 Guillaume Thouvenin
2005-05-09 9:31 ` Alexander Nyberg
2005-05-09 11:38 ` Guillaume Thouvenin
2005-05-09 11:48 ` Evgeniy Polyakov
2005-05-09 21:08 ` Andrew Morton
2005-05-09 21:43 ` Evgeniy Polyakov
2005-05-10 11:13 ` aq
2005-05-10 11:24 ` Evgeniy Polyakov
2005-05-09 12:00 ` Nick Piggin [this message]
2005-05-09 12:22 ` Alexander Nyberg
2005-05-09 12:43 ` Guillaume Thouvenin
2005-05-09 13:13 ` Guillaume Thouvenin
2005-05-09 13:32 ` aq
2005-05-09 13:57 ` Alexander Nyberg
2005-05-11 11:44 ` Guillaume Thouvenin
2005-05-10 11:18 ` Guillaume Thouvenin
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=427F50DB.2020705@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=aquynh@gmail.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=guillaume.thouvenin@bull.net \
--cc=jlan@engr.sgi.com \
--cc=johnpol@2ka.mipt.ru \
--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
Powered by JetHome