xfs
[Top] [All Lists]

Re: hangs running dbench with 16 clients

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: hangs running dbench with 16 clients
From: Nicholas Wourms <nwourms@xxxxxxxxxxxxx>
Date: Thu, 19 Jun 2003 16:14:07 -0400
Cc: Steven Pratt <slpratt@xxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056037205.1773.101.camel@jen.americas.sgi.com> <20030619195239.GB13952@wotan.suse.de>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.2) Gecko/20030208 MultiZilla/v1.1.20
Andi Kleen wrote:
2.5 is not getting as much air time - and kdb does not work which


http://www.ccur.com/realtime/oss/ has a 2.5.69 kdb which could be probably used with .72 with minor changes.

But I can recommend kgdb, which in its latest iterations (e.g. the one in the -mm tree) is more powerful and of course
is source level.



Well that's all fine & good if you have the extra dumb (or not-so-dumb) terminals lying around to use it, but not everyone does. Furthermore, getting things "set-up" for kgdb is just a PITA compared to kdb just working as OOOPS happen (again, who wants to dedicate a machine to kgdb full-time?). Perhaps what might be done is to merge the two debuggers to give the user the choice of in-kernel debugging or remote core debugging. In other words, make the debugging of ooops/panics a boot argument? I don't know much about kgdb, so as to how practical this might be is another question.


Cheers,
Nicholas

P.S. - Thanks for the link to the updated patch, been waiting for something like this for awhile...


<Prev in Thread] Current Thread [Next in Thread>