From: Joel Soete <soete.joel@scarlet.be>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Parisc List <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] [PATCH] make parisc interrupts nest properly
Date: Tue, 05 Sep 2006 19:14:33 +0000 [thread overview]
Message-ID: <44FDCC99.2040805@scarlet.be> (raw)
In-Reply-To: <1157425332.3513.35.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Mon, 2006-09-04 at 22:55 -0400, Carlos O'Donell wrote:
>
>>This patch looks great. What boxes have you tested this with? 32-bit?
>>64-bit?
>
>
> The only one I currently have access to: a pa8800 (i.e. 64 bit).
>
duno if that could help: I tested it on b2k 32bit kernel and c110.
I did noticed build pb nor boot ;-)
Just compare on b2k the time to build the same kernel tree (same config):
without patch:
real 30m43.031s
user 26m17.318s
sys 3m58.584s
with patch:
real 31m14.598s
user 26m9.790s
sys 4m40.426s
imho no significant differences.
Joel
> There's some testing to do to make sure I haven't disturbed any of the
> other bus types, so I'll try it out on my raven when I get that up, but,
> unfortunately, the dino block of interrupts, because of the way they're
> wired, won't be able to interrupt each other.
>
> James
>
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
>
>
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
prev parent reply other threads:[~2006-09-05 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 17:32 [parisc-linux] [PATCH] make parisc interrupts nest properly James Bottomley
2006-09-05 2:55 ` Carlos O'Donell
2006-09-05 3:02 ` James Bottomley
2006-09-05 19:14 ` Joel Soete [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=44FDCC99.2040805@scarlet.be \
--to=soete.joel@scarlet.be \
--cc=James.Bottomley@SteelEye.com \
--cc=parisc-linux@lists.parisc-linux.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