From: Finn Thain <fthain@telegraphics.com.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: m68k: Convert to genirq (WIP)
Date: Fri, 17 Jun 2011 13:45:24 +1000 (EST) [thread overview]
Message-ID: <alpine.OSX.2.00.1106171337170.191@ibook.intranet> (raw)
In-Reply-To: <BANLkTik5-H1fc2rk3QrwvQiF=7fELmE2CA@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1307 bytes --]
On Thu, 16 Jun 2011, Geert Uytterhoeven wrote:
> On Wed, Jun 15, 2011 at 21:44, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Sat, Jun 4, 2011 at 19:56, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >> On Sat, May 28, 2011 at 20:32, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >>
> >> It works on Amiga now, too. It can still use some optimizations in
> >> the irq_{enable,disable,ack,mask,mask_ack,unmask} area, as my
> >> BogoMIPS rating dropped by ca 2.5% and is now under 16, for a 25 MHz
> >> 68040.
> >
> > Seems like everything (Atari/ARAnyM and Amiga) still works when using
> > handle_simple_irq instead of handle_level_irq. As a bonus, BogoMIPS is
> > above 16 again.
Your bogomips benchmark would be the best-case penalty, right?
Have you tried say, sending a ping flood to measure throughput and
latency?
>
> With handle_simple_irq(), we no longer need to define irq_{,un}mask()
> methods in our irq_chips. Hence the "old" m68k platform interrupt code
> seems to be much closer to genirq than I thought...
>
> Does this make sense?
If the simple irq model gets us closer to the goal and doesn't kill
performance then it makes sense to me.
Finn
>
> Gr{oetje,eeting}s,
>
> Geert
>
next prev parent reply other threads:[~2011-06-17 3:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 18:32 m68k: Convert to genirq (WIP) Geert Uytterhoeven
2011-05-31 8:35 ` Geert Uytterhoeven
2011-05-31 9:50 ` Thomas Gleixner
2011-05-31 19:54 ` Geert Uytterhoeven
2011-05-31 20:10 ` Thomas Gleixner
2011-06-03 11:20 ` Finn Thain
2011-06-03 11:33 ` Geert Uytterhoeven
2011-06-05 6:27 ` Brad Boyer
2011-06-05 7:45 ` Geert Uytterhoeven
2011-08-10 9:59 ` Geert Uytterhoeven
2011-08-10 10:53 ` Finn Thain
2011-08-10 16:19 ` Brad Boyer
2011-08-26 9:52 ` Geert Uytterhoeven
2011-08-26 11:21 ` Finn Thain
2011-08-26 11:32 ` Geert Uytterhoeven
2011-08-26 16:09 ` Brad Boyer
2011-06-04 17:56 ` Geert Uytterhoeven
2011-06-15 19:44 ` Geert Uytterhoeven
2011-06-16 19:30 ` Geert Uytterhoeven
2011-06-16 20:03 ` Thomas Gleixner
2011-06-17 3:45 ` Finn Thain [this message]
2011-06-17 5:01 ` Geert Uytterhoeven
2011-08-08 13:08 ` Geert Uytterhoeven
2011-08-10 10:48 ` Finn Thain
2011-06-16 19:45 ` Geert Uytterhoeven
2011-06-16 21:10 ` Michael Schmitz
2011-06-17 17:25 ` Andreas Schwab
2011-06-17 17:22 ` Andreas Schwab
2011-06-19 10:17 ` Geert Uytterhoeven
2011-06-19 11:19 ` Andreas Schwab
2011-06-19 13:36 ` Geert Uytterhoeven
2011-06-19 13:58 ` Andreas Schwab
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.1106171337170.191@ibook.intranet \
--to=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=tglx@linutronix.de \
/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