From: Ingo Molnar <mingo@elte.hu>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] kmemcheck: divide and conquer
Date: Sat, 14 Jun 2008 08:31:14 +0200 [thread overview]
Message-ID: <20080614063114.GA24188@elte.hu> (raw)
In-Reply-To: <20080613140057.GA25833@damson.getinternet.no>
* Vegard Nossum <vegard.nossum@gmail.com> wrote:
> Hi,
>
> I've split the main x86/mm/kmemcheck.c file and made a subdirectory of
> many files instead.
>
> I have included the diffstat below, but I think the patch itself is
> too big for the mailing list. It can instead be viewed at:
>
> http://www.kernel.org/pub/linux/kernel/people/vegard/patches/0001-kmemcheck-divide-and-conquer.patch
>
> The RFC part: Is this a good thing to do? I personally hate the
> 4000-line files that are so commonly found in the kernel, and
> therefore prefer this split-up. On the other hand, C lacks namespaces,
> which sometimes leads to some really long and ugly names just to
> prevent clashes in the future. But it's your call, I'll just do
> whatever it takes to get in... ;-)
it's a very nice splitup! :-) [ Any Git coordinates to pick it up? ]
such a splitup opens up for future enhancements such as the sharing of
opcode decoding between kmemcheck, mmiotrace and KVM. It also makes the
code easier to maintain as there's less risk of patch merge conflicts.
And not the least, it's easier to read as well if it's split up into
logical modules.
Ingo
next prev parent reply other threads:[~2008-06-14 6:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 14:00 [RFC][PATCH] kmemcheck: divide and conquer Vegard Nossum
2008-06-14 6:31 ` Ingo Molnar [this message]
2008-06-14 8:39 ` Vegard Nossum
2008-06-14 9:00 ` Ingo Molnar
2008-06-14 9:17 ` Vegard Nossum
2008-06-16 5:15 ` Ingo Molnar
2008-06-16 6:55 ` Vegard Nossum
2008-06-16 7:10 ` Ingo Molnar
2008-06-16 7:20 ` Vegard Nossum
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=20080614063114.GA24188@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.