From: David Newall <davidn@davidnewall.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for mm] Remove iBCS support
Date: Fri, 25 Jan 2008 12:44:05 +1030 [thread overview]
Message-ID: <479945ED.7040007@davidnewall.com> (raw)
In-Reply-To: <20080124181442.GE4476@does.not.exist>
Adrian Bunk wrote:
> On Fri, Jan 25, 2008 at 04:25:24AM +1030, David Newall wrote:
>
>> The performance benefit is trivial, and the improvement to
>> maintainability is even less.
>>
>
> The effects become bigger when you realize that there are many such
> places in the kernel.
>
> And the benefit of keeping it is zero.
>
The benefit is not zero. Repeating myself: While the code is there, it
encourages either removal or repair. If the option to remove is taken
off the table then it will eventually be repaired.
> What you are doing is not contributing but wasting other people's time.
>
You want to remove the code so you attack me. Sadly for you, your
personal taste is irrelevant to the benefit that I bring. What kind of
a person considers robust debate to be a waste of time? A bit
pathetic, sadly.
> The only thing you could ever achieve with this kind of "contribution"
> is to end up in some killfiles.
>
I'm comfortable with that. I'm also comfortable that consensus might go
against me. This childish threat of kill-files is not going to stop me.
>>>> At one stage iBCS2 support DID work. Now it doesn't. Now there's an
>>>> argument that the remaining infrastructure should be removed. This is
>>>> the wrong direction to take.
>>>>
>>>>
>>> When did iBCS2 support work in a plain ftp.kernel.org kernel?
>>>
>>>
>> I don't know when. Are you disputing that it ever did? I think it's a
>> given that once it worked.
>>
>
> AFAIK the kernel never shipped with iBCS2 support.
>
Are you claiming that it never did? Is that even important? Clearly
there was support for it in the mainline kernel. Anecdotally the
support worked.
...
> The point is that ideas do not turn themselves into code.
>
This discussion is about removing code. That's a bit like tearing down
the pergola because the vine has shrivelled. Easy to do, but
counter-productive. LIkewise, removing iBCS2 code would be
unproductive. It would achieve no benefit, whilst simultaneously
leading Linux in the wrong direction. This is a point you have
consistently failed to address.
> And there are far too many people who want to see their great ideas
> implemented without implementing it themselves.
>
This is not about a great idea. It's about a pointless idea. Even
allowing what you say to be true, and it probably is, there is nothing
wrong with somebody having a great idea and leaving it to others to
implement. If the only people allowed to have great ideas were those
who could implement them then the world would be a much poorer place.
You demonstrate a twisted view of value.
> Talking about a feature without having anyone willing to implement it
> simply has no value.
Who said nobody is willing to implement it? We've all recently learned
that there is a patch. From there to implementation is much closer than
you or I thought last week. So already this discussion has prompted
tangible benefit.
next prev parent reply other threads:[~2008-01-25 2:14 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 4:59 [PATCH for mm] Remove iBCS support Andi Kleen
2008-01-20 2:27 ` David Newall
2008-01-20 3:11 ` Andi Kleen
2008-01-20 4:46 ` David Newall
2008-01-20 5:18 ` Andi Kleen
2008-01-20 5:33 ` David Newall
2008-01-20 5:55 ` Andi Kleen
2008-01-20 6:23 ` David Newall
2008-01-20 7:29 ` Andi Kleen
2008-01-21 1:37 ` David Newall
2008-01-22 10:24 ` Karl Kiniger
2008-01-22 15:06 ` David Newall
2008-01-22 15:52 ` Adrian Bunk
2008-01-23 8:48 ` Andi Kleen
2008-01-23 14:12 ` Karl Kiniger
2008-01-23 14:24 ` Andi Kleen
2008-01-24 17:06 ` David Newall
2008-01-22 11:12 ` Ingo Molnar
2008-01-22 12:42 ` Karl Kiniger
2008-01-22 15:13 ` David Newall
2008-01-22 15:49 ` Ingo Molnar
2008-01-24 17:01 ` David Newall
2008-01-22 16:01 ` Adrian Bunk
2008-01-24 17:04 ` David Newall
2008-01-24 17:24 ` Adrian Bunk
2008-01-24 17:55 ` David Newall
2008-01-24 18:14 ` Adrian Bunk
2008-01-25 2:14 ` David Newall [this message]
2008-01-25 5:12 ` Valdis.Kletnieks
2008-01-25 16:40 ` Alan Cox
2008-01-24 19:51 ` Pavel Machek
2008-01-25 2:17 ` David Newall
2008-01-24 20:37 ` Andi Kleen
2008-01-25 2:16 ` David Newall
2008-01-22 16:50 ` Alan Cox
2008-01-24 17:08 ` David Newall
2008-01-22 13:20 ` Giulio
2008-01-20 13:06 ` Alan Cox
2008-01-20 13:43 ` David Newall
2008-01-20 13:51 ` Alan Cox
2008-01-25 12:17 ` Ingo Molnar
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=479945ED.7040007@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.