public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: mike <localgost@gmail.com>
Cc: linux-m68k@vger.kernel.org, debian-68k@lists.debian.org
Subject: Re: toolchain, was Re: bogl: don't know screen type 1
Date: Sun, 6 Sep 2009 20:00:01 +1000 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.00.0909061901140.415@silk.local> (raw)
In-Reply-To: <8259f0250909050900u3f367519tadcd44bd41779dd4@mail.gmail.com>


On Sat, 5 Sep 2009, mike wrote:

> > The life is fast ebbing from debian/m68k as far as I can tell. I'm not 
> > sure if there is sufficient energy to revitalize it. I'd be delighted 
> > to be proven wrong.
> 
> Yep sad isnt it, one hope for the port is that several amigans ( trough 
> natami ) and atarians ( trough the coldfire atari project) or otherwise 
> some miracle happens at freescale and thereby more people see a reason 
> to run debian on their 68k's,
> 
> Question is tho, as the kernel gets more bloated and slower as time 
> passes, and the packages that run on top, will it even be usable on 
> those in a few...

I haven't seen anyone test for kernel performance regressions on m68k 
(other than the scheduler regression) -- let alone work on reversing them. 
Probably because of the usual shortage of skills.

> Netbsd seems to have a fast kernel. from what little i've booted of 
> it...

You have to pick the right architecture. In Linux (the kernel) algorithms 
are tuned for the common case, which is x86. And hence you'd expect a 
Linux operating system's performance to be competitive with any equivalent 
operating system running on that architecture.

Having said that, kernel performance even on x86 is quite variable from 
one release to another:
http://www.phoronix.com/scan.php?page=article&item=linux_2629_benchmarks&num=9 

Of course, benchmarks on Intel architectures should not be taken as 
representative of m68k performance. It would be informative to build and 
run a benchmark suite like that one on debian etch-m68k (it has gcc 3.3 
and 4.1) using the latest kernel.

Finn

  reply	other threads:[~2009-09-06  9:59 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  3:28 bogl: don't know screen type 1 mike
2009-08-31 12:06 ` Stephen R Marenka
2009-08-31 12:58   ` mike
2009-08-31 22:11     ` mike
2009-08-31 22:16       ` mike
2009-09-01 15:17         ` Stephen R Marenka
2009-09-03  1:16           ` mike
2009-09-03  1:22             ` mike
2009-09-03  9:50               ` Maxim Kuvyrkov
2009-09-03 16:41                 ` mike
2009-09-11 20:01               ` Kolbjørn Barmen
2009-09-11 20:25                 ` Geert Uytterhoeven
2009-09-12 10:24                 ` fthain
2009-09-04 15:43           ` toolchain, was " Finn Thain
2009-09-05  1:08             ` Stephen R Marenka
2009-09-05  1:57               ` mike
2009-09-05  2:17                 ` mike
2009-09-05  7:08               ` Petr Stehlik
2009-09-05  8:49               ` Ingo Jürgensmann
2009-09-06  5:07               ` Finn Thain
2009-09-05 13:31             ` Maxim Kuvyrkov
2009-09-05 16:00               ` mike
2009-09-06 10:00                 ` Finn Thain [this message]
2009-09-06  2:37               ` toolchain Finn Thain
2009-09-06 23:09                 ` toolchain Stephen R Marenka
2009-09-06  5:20               ` toolchain Finn Thain
2009-09-08 13:07                 ` toolchain Finn Thain
2009-09-13  3:38               ` toolchain, was Re: bogl: don't know screen type 1 fthain
2009-09-13  5:01                 ` Maxim Kuvyrkov
2009-09-14 10:37                   ` fthain
2009-09-22  5:11                     ` mike
2009-09-22 13:09                       ` benchmarks, was Re: toolchain Finn Thain
2009-09-22 14:51                         ` mike
2009-09-22 15:08                           ` Geert Uytterhoeven
2009-09-28 14:00                       ` toolchain, was Re: bogl: don't know screen type 1 mike
2009-09-28 14:26                         ` debian installation Finn Thain
2009-09-28 14:44                           ` mike
2009-09-29  9:45                             ` mike
2009-09-29 22:23                               ` Rolf Anders

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=alpine.OSX.2.00.0909061901140.415@silk.local \
    --to=fthain@telegraphics.com.au \
    --cc=debian-68k@lists.debian.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=localgost@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox