LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, dada1@cosmosbay.com,
herbert@gondor.apana.org.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: include/linux/pcounter.h
Date: Wed, 27 Feb 2008 22:27:30 -0300 [thread overview]
Message-ID: <20080228012730.GN4725@ghostprotocols.net> (raw)
In-Reply-To: <20080227073650.GC4638@elte.hu>
Em Wed, Feb 27, 2008 at 08:36:50AM +0100, Ingo Molnar escreveu:
>
> * David Miller <davem@davemloft.net> wrote:
>
> > > but the main and fundamental question still remains unanswered (more
> > > than 3 weeks after Andrew asked that question): why was this piece
> > > of general infrastructure merged via net.git and not submitted to
> > > lkml ever? The code touching -mm does _not_ count as "review".
> >
> > I already stated this was a mistake and it won't happen again in the
> > future.
>
> sorry - that bit of the thread didnt seem to make it to lkml. I just saw
> this incomplete discussion with a denial and with no resolution.
>
> And you did the right thing anyway by thinking in terms of a generic
> piece of infrastructure instead of hiding it away into say
> include/net/pcounter.h (which nobody could have objected against).
>
> I sometimes think that the forced isolation of subsystems (rather
> strongly enforced both by -mm and by linux-next) and their hiding away
> on non-lkml lists will eventually hurt the core kernel because less and
> less people will be willing to go the trouble of doing proper
> cross-subsystem development. That results in duplicated or specialistic
> infrastructure, increased code size and longer term, ultimately less
> performance. (by the time we notice _that_ it will probably be too late
> to do anything about it)
This more friendly wording makes me feel actually happy to get from my
hiding place and tell that I actually saw the percpu counters code, just
after I made Eric's code generic as I thought it should have been from
the start, I found out about what was already in lib/.
I just got lazy to do what at the time looked the right thing
to do: to read thru the existing lib/ code and use it where pcounter was
being used. But at least it got exposed 8-)
Anyway, progress was made, I do not feel too bad about it even now.
- Arnaldo
prev parent reply other threads:[~2008-02-28 1:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 9:44 include/linux/pcounter.h Andrew Morton
2008-02-05 0:20 ` include/linux/pcounter.h David Miller
2008-02-05 0:43 ` include/linux/pcounter.h Andrew Morton
2008-02-16 3:37 ` include/linux/pcounter.h Andrew Morton
2008-02-16 10:07 ` include/linux/pcounter.h Eric Dumazet
2008-02-16 10:50 ` include/linux/pcounter.h Andrew Morton
2008-02-16 12:03 ` include/linux/pcounter.h Eric Dumazet
2008-02-16 19:26 ` include/linux/pcounter.h Andrew Morton
2008-02-16 19:39 ` include/linux/pcounter.h Arjan van de Ven
2008-02-17 5:54 ` include/linux/pcounter.h David Miller
2008-02-26 9:24 ` include/linux/pcounter.h Ingo Molnar
2008-02-26 21:35 ` include/linux/pcounter.h David Miller
2008-02-27 7:36 ` include/linux/pcounter.h Ingo Molnar
2008-02-28 1:27 ` Arnaldo Carvalho de Melo [this message]
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=20080228012730.GN4725@ghostprotocols.net \
--to=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--subject='Re: include/linux/pcounter.h' \
/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
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).