linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch] eliminate CLONE_* duplications
Date: Tue, 27 Sep 2005 18:22:42 +0200	[thread overview]
Message-ID: <20050927162242.GC21927@MAIL.13thfloor.at> (raw)
In-Reply-To: <Pine.LNX.4.61.0509271705380.3728@scrub.home>

On Tue, Sep 27, 2005 at 05:25:41PM +0200, Roman Zippel wrote:
> Hi,
> 
> (Sorry for the delay.)

no big deal ...

> On Thu, 22 Sep 2005, Herbert Poetzl wrote:
> 
> > _what_ do you consider 'logically organized' because
> > putting all the CLONE_* stuff into a separate file is
> > pretty logical for me ... but obviously not for you.
> 
> "logically organized" mainly means reducing dependencies by organizing
> them by their logical dependencies. 

did you consider that separating out the clone
stuff might be that basis for reducing dependencies?

> If a large header file is included by a lot of other files, some parts
> maybe separated to reduce header dependencies. The same can be done
> for config dependencies, so that a config change doesn't necessarily
> recompiles the whole kernel.

> Your change doesn't reduce any dependecies and it's not such a big 
> cleanup:

aha, so we want a big all-in-one patch now which
does many changes at once, instead of a small
(and obvious) cleanup first, then later maybe
a restructuring ... yes?

>  arch/alpha/kernel/asm-offsets.c         |    2 --
>  arch/alpha/kernel/entry.S               |    1 +
>  arch/cris/arch-v10/kernel/asm-offsets.c |    3 ---
>  arch/cris/arch-v10/kernel/entry.S       |    1 +
>  arch/cris/arch-v32/kernel/asm-offsets.c |    3 ---
>  arch/frv/kernel/kernel_thread.S         |    2 +-
>  arch/ia64/ia32/ia32_entry.S             |    3 ++-
>  arch/ia64/kernel/asm-offsets.c          |    4 ----
>  arch/parisc/kernel/entry.S              |    4 +---
>  arch/ppc/kernel/asm-offsets.c           |    2 --
>  arch/ppc/kernel/misc.S                  |    1 +
>  arch/ppc64/kernel/asm-offsets.c         |    3 ---
>  arch/ppc64/kernel/misc.S                |    1 +
>  arch/v850/kernel/asm-offsets.c          |    4 ----
>  arch/v850/kernel/entry.S                |    1 +
>  include/asm-cris/arch-v10/offset.h      |    3 ---
>  include/asm-cris/arch-v32/offset.h      |    3 ---
>  include/linux/clone.h                   |   32 ++++++++++++++++++++++++++++++++
>  include/linux/sched.h                   |   30 +-----------------------------
>  19 files changed, 42 insertions(+), 61 deletions(-)

> The noise generated by the separation is larger than the avoided 
> duplication.

hmm, interesting argument ...

> The hardcoded defines actually do need fixing, frv is especially bad,
> as it even has hardcoded structure offsets.

so instead of fixing the issue properly, we 
'mend' it by adding new code to */asm-offsets.c

> > I have absolutely no problem with different, more
> > logical splitups, and I'm willing to break down the
> > entire sched.h if that will help the cause ... so
> > please enlighten me here ...

> sched.h is especially challenging due to dependencies between headers
> under asm and linux. It's not just splitting sched.h, it also requires
> analyzing its dependencies.

which you obviously think is nothing I can do
'properly' ...

thanks for the info,
Herbert

> bye, Roman

  reply	other threads:[~2005-09-27 16:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-21  9:21 [Patch] eliminate CLONE_* duplications Herbert Poetzl
2005-09-21 10:55 ` Roman Zippel
2005-09-21 14:39   ` Herbert Poetzl
2005-09-21 14:53     ` Roman Zippel
2005-09-21 15:11       ` Herbert Poetzl
2005-09-21 15:39         ` Roman Zippel
2005-09-21 23:58           ` Herbert Poetzl
2005-09-27 15:25             ` Roman Zippel
2005-09-27 16:22               ` Herbert Poetzl [this message]
2005-09-27 17:04                 ` Roman Zippel

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=20050927162242.GC21927@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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).