Hi,
I am able to backport kern_ktr.c and related files and ktrdump to
versions older than 5.0 specially 4.1
with non-SMP configuration file kern_ktr.c file is compiled
successfully.
But with SMP configuration file it is giving an assembly errors as follows :
cc -c -O -march=pentiumpro
On Wed, 7 Sep 2005, Nikhil Dharashivkar wrote:
I went through the ktr and ktrdump options. I compiled the kernel
with options ktr. I found that ktr support is mostly for lock and
schedule. We can trace drivers using mask KTR_DEV and some CTR*
statements in dirver.
But This ktr support
Hi,
I went through the ktr and ktrdump options. I compiled the kernel
with options ktr.
I found that ktr support is mostly for lock and schedule. We can trace
drivers using mask KTR_DEV and some CTR* statements in dirver.
But This ktr support is from freebsd 5. I am aslo using freebsd
4.10
On Tue, 6 Sep 2005, Nikhil Dharashivkar wrote:
Yes, it is ok if i loose data in ktrace queue when crash occurs.
Basically, I want to give an Disk IO trace support to ktrace on FreeBSD.
So, what I am thinking to use struct dio in dastrategy routine to
trace the IO. I 'll use this struct to
On Tue, 6 Sep 2005, Peter Jeremy wrote:
On Tue, 2005-Sep-06 10:33:53 +0530, Nikhil Dharashivkar wrote:
Thanks for replying me. Basically what happend, while testing
scsi driver on freebsd, at some point it crashes. So, there is no way
to know how much IO is performed. To know the IO state
Scott Long wrote:
Nikhil Dharashivkar wrote:
Hi,
i want to hack the ktrace system call. Basically, I want to monitor
scsi disk IO through dastrategy() routine.
It seems that kern_ktrace.c implements different functions for
ktrace options like -tc / -ti ... etc (see man page). So, is it
Sorry it's struct bio instead of struct dio.
On 9/6/05, Nikhil Dharashivkar <[EMAIL PROTECTED]> wrote:
> Yes, it is ok if i loose data in ktrace queue when crash occurs.
> Basically, I want to give an Disk IO trace support to ktrace on
> FreeBSD.
>So, what I am thinking to use struct dio
Yes, it is ok if i loose data in ktrace queue when crash occurs.
Basically, I want to give an Disk IO trace support to ktrace on
FreeBSD.
So, what I am thinking to use struct dio in dastrategy
routine to trace the IO.
I 'll use this struct to generate ktr_request. Throught
ktr_writereques
On Tue, 2005-Sep-06 10:33:53 +0530, Nikhil Dharashivkar wrote:
> Thanks for replying me. Basically what happend, while testing
>scsi driver on freebsd, at some point it crashes. So, there is no way
>to know how much IO is performed. To know the IO state just before the
>driver fails, i selecte
Crashed occured only once at client side, for some long duration test.
But it is informed that at some point to monitor the testing report
should have some IO trace.
On 9/6/05, Scott Long <[EMAIL PROTECTED]> wrote:
> Nikhil Dharashivkar wrote:
> > Hi Scott and Rajesh,
> > Thanks for reply
Nikhil Dharashivkar wrote:
Hi Scott and Rajesh,
Thanks for replying me. Basically what happend, while testing
scsi driver on freebsd, at some point it crashes. So, there is no way
to know how much IO is performed. To know the IO state just before the
driver fails, i selected ktrace to print
Hi Scott and Rajesh,
Thanks for replying me. Basically what happend, while testing
scsi driver on freebsd, at some point it crashes. So, there is no way
to know how much IO is performed. To know the IO state just before the
driver fails, i selected ktrace to print IO information whatever i ll
Nikhil Dharashivkar wrote:
Yes, what rajesh saying is right , i want to print IO Bytes.
You want to capture writes coming from userland, or you want to
capture all low-level disk writes? Are you trying to correlate
these writes with a particular user process? Consider an mmaped
file. A userl
Yes, what rajesh saying is right , i want to print IO Bytes.
On 9/6/05, Scott Long <[EMAIL PROTECTED]> wrote:
> Rajesh S. Ghanekar wrote:
> > Scott Long wrote:
> >
> >> Nikhil Dharashivkar wrote:
> >>
> >>> Hi,
> >>>i want to hack the ktrace system call. Basically, I want to monitor
> >>> scsi
Rajesh S. Ghanekar wrote:
Scott Long wrote:
Nikhil Dharashivkar wrote:
Hi,
i want to hack the ktrace system call. Basically, I want to monitor
scsi disk IO through dastrategy() routine.
It seems that kern_ktrace.c implements different functions for
ktrace options like -tc / -ti ... etc
Nikhil Dharashivkar wrote:
Hi,
i want to hack the ktrace system call. Basically, I want to monitor
scsi disk IO through dastrategy() routine.
It seems that kern_ktrace.c implements different functions for
ktrace options like -tc / -ti ... etc (see man page). So, is it
possible to add new o
Hi,
i want to hack the ktrace system call. Basically, I want to monitor
scsi disk IO through dastrategy() routine.
It seems that kern_ktrace.c implements different functions for
ktrace options like -tc / -ti ... etc (see man page). So, is it
possible to add new option for disk IO with new st
17 matches
Mail list logo
