From: "Joseph D. Wagner" <theman@josephdwagner.info>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FEATURE REQUEST: Specific Processor Optimizations on x86 Architecture
Date: Wed, 22 Oct 2003 19:47:45 +0600 [thread overview]
Message-ID: <200310221947.45996.theman@josephdwagner.info> (raw)
In-Reply-To: <20031023001547.GA18395@redhat.com>
> Already done for 2.6
Version 2.6 is still in beta. Besides, this should have been done years ago
before 2.6 existed.
> Last time I looked these made absolutely no difference to performance
> due to the only differences being on FP code.
So what? Some other kernel developer -- like a module/driver developer, a
real-time systems developer, a simulations developer, or just some guy
messing around (read: student) -- might really want or even need those
specific optimizations.
Isn't this whole free-as-in-freedom software thing about giving developers
and end-users options they wouldn't otherwise have under closed source
alternatives? In that spirit, shouldn't developers have the option of
optimizing for those specific processors?
And don't give me this crap that being open source means I can do it myself.
The fact is that most people can't make the changes themselves. Then,
instead of chosing between an operating system they like and an operating
system they hate, people end up choosing between an operating system they
hate and an operating system they really hate.
This is one of the reasons why I've never contributed to any open source
project: the my-way-or-the-highway attitude of the existing developer base
makes attempts for newbies to get inside an invintation for unnecessary
pain.
Unless there's some hidden section of makefile code I don't know about, you
can count the number of lines that would have to be changed to meet my
request on the fingers of one of your hands. If you don't make the change,
I will consider it conclusive proof that the whole free-as-in-freedom is
really just free-as-in-beer.
Joseph D. Wagner
next prev parent reply other threads:[~2003-10-23 0:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 12:55 Joseph D. Wagner
2003-10-23 0:12 ` Måns Rullgård
2003-10-22 13:26 ` Joseph D. Wagner
2003-10-23 0:37 ` Michael Rozhavsky
2003-10-23 0:15 ` Dave Jones
2003-10-22 13:47 ` Joseph D. Wagner [this message]
2003-10-23 1:02 ` Rik van Riel
2003-10-23 1:14 ` Joseph D. Wagner
2003-10-23 1:18 ` Rik van Riel
2003-10-23 9:26 ` Jan-Benedict Glaw
2003-10-23 9:35 ` Måns Rullgård
2003-10-23 1:06 ` Tim Hockin
2003-10-22 15:40 ` Joseph D. Wagner
2003-10-23 14:57 ` Rik van Riel
2003-10-23 1:23 ` Dave Jones
2003-10-22 15:35 ` Joseph D. Wagner
2003-10-23 2:52 ` William Lee Irwin III
2003-10-23 9:35 ` Jan-Benedict Glaw
2003-10-23 13:40 ` Jesse Pollard
2003-10-23 14:57 ` Charles Cazabon
2003-10-23 15:34 ` David Zaffiro
2003-10-23 17:26 ` Rob
2003-10-23 23:05 ` J.A. Magallon
2003-10-23 23:24 ` Nick Piggin
[not found] ` <200310241301.41230.ioe-lkml@rameria.de>
2003-10-27 15:20 ` J.A. Magallon
2003-10-27 20:52 ` Zwane Mwaikambo
[not found] <JB3R.23s.23@gated-at.bofh.it>
[not found] ` <JBn4.2xt.19@gated-at.bofh.it>
[not found] ` <JBPW.36x.3@gated-at.bofh.it>
2003-10-23 8:32 ` Ihar 'Philips' Filipau
2003-10-23 8:37 ` Ihar 'Philips' Filipau
[not found] ` <JWKQ.7nS.15@gated-at.bofh.it>
[not found] ` <LhtX.bs.15@gated-at.bofh.it>
[not found] ` <LhtX.bs.13@gated-at.bofh.it>
2003-10-27 18:33 ` Andi Kleen
2003-10-27 21:05 ` Zwane Mwaikambo
[not found] <JB3R.23s.23@gated-at.bofh.it.suse.lists.linux.kernel>
[not found] ` <JWKQ.7nS.15@gated-at.bofh.it.suse.lists.linux.kernel>
[not found] ` <LhtX.bs.15@gated-at.bofh.it.suse.lists.linux.kernel>
[not found] ` <LhtX.bs.13@gated-at.bofh.it.suse.lists.linux.kernel>
[not found] ` <m3k76qsf8i.fsf@averell.firstfloor.org.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.53.0310271603580.21953@montezuma.fsmlabs.com.suse.lists.linux.kernel>
2003-10-27 21:15 ` Andi Kleen
2003-11-18 14:28 ` Zwane Mwaikambo
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=200310221947.45996.theman@josephdwagner.info \
--to=theman@josephdwagner.info \
--cc=davej@redhat.com \
--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
all inboxes | Powered by JetHome®