G'Day Folks,
On Fri, Jan 18, 2008 at 04:52:58PM -0500, Bryan Cantrill wrote:
>
> On Fri, Jan 18, 2008 at 04:33:17PM -0500, Colin Burgess wrote:
> > I see Intel has released a new tool. Oh, it requires some patches to
> > the kernel to record
> > latency times. Good thing people don't mind patc
Well I see that Brendan did reply to the OSNews link to this. He basically
shot them down at hardcoding the instrumentation - as he should have! :-)
Shame on Intel - they should know better!
Colin
Bryan Cantrill wrote:
On Fri, Jan 18, 2008 at 04:33:17PM -0500, Colin Burgess wrote:
> I see I
Hello. I would like to ask for some help on a dtrace script I am writing.
The following set of dtrace functions seems not to workI see output
for the entry function as expected, but I do not see a corresponding
return value being returned. Actually the return function was more
complicate
On Fri, 2008-01-18 at 16:33 -0500, Colin Burgess wrote:
> I see Intel has released a new tool. Oh, it requires some patches to
> the kernel to record
> latency times. Good thing people don't mind patching their kernels, eh?
>
> So who can write the equivalent latencytop.d the fastest? ;-)
>
>
On Fri, Jan 18, 2008 at 04:33:17PM -0500, Colin Burgess wrote:
> I see Intel has released a new tool. Oh, it requires some patches to
> the kernel to record
> latency times. Good thing people don't mind patching their kernels, eh?
>
> So who can write the equivalent latencytop.d the fastest? ;
On Fri, Jan 18, 2008 at 11:06:33AM -0800, eric kustarz wrote:
> >>Any plans for the ancillary protocols of NFSv3 (NLM, MOUNT, stat,
> >>acl)? This would allow us to have a true "nfsv3_snoop.d".
> >
> >No immediate plans. What would be needed?
>
> Same thing you did for NFSv4 and are doing for NFS
On Jan 17, 2008, at 4:28 PM, Adam Leventhal wrote:
> On Thu, Jan 17, 2008 at 04:17:25PM -0800, eric kustarz wrote:
>> This is for just the NFSv3 server (as opposed to the client and
>> server), right?
>
> Just the server. We have designs for client providers, but we
> (obviously)
> don't need t
Ok--I may have found the problem (easy)--I had assumed self->path was
always non-NULL.
Thanks anyway!!
Janice
Janice Chang wrote:
> Hello. I would like to ask for some help on a dtrace script I am writing.
>
> The following set of dtrace functions seems not to workI see output
> for the e
I see Intel has released a new tool. Oh, it requires some patches to
the kernel to record
latency times. Good thing people don't mind patching their kernels, eh?
So who can write the equivalent latencytop.d the fastest? ;-)
http://www.latencytop.org/
--
[EMAIL PROTECTED]
___
LOL - you rock, Brendan.
You know, at the VERY least they could have used systemtap, I guess.
Colin
Brendan Gregg - Sun Microsystems wrote:
G'Day Folks,
On Fri, Jan 18, 2008 at 04:52:58PM -0500, Bryan Cantrill wrote:
>
> On Fri, Jan 18, 2008 at 04:33:17PM -0500, Colin Burgess wrote:
> > I
10 matches
Mail list logo
