questing: delay of a context - switch

Hi Dose anyone know how long a the kernel is buisy with context switching (beetween two processes) ? Has anyone testet this yet? I have made estimate of 7 usec duration for that, (on a Pentium 400) but I think that's to long. Regards Thomas To Unsubscribe: send mail to majord...@freeb

question: delay of a context - switch

Hi Dose anyone know how long a the kernel is busy with context switching (beetween two processes) ? Has anyone tested this yet? I estimate of about 7 usec duration for that, (on a Pentium 400) but I think that's to long. Regards Thomas To Unsubscribe: send mail to majord...@freebsd.or

questing: delay of a context - switch

Hi Dose anyone know how long a the kernel is buisy with context switching (beetween two processes) ? Has anyone testet this yet? I have made estimate of 7 usec duration for that, (on a Pentium 400) but I think that's to long. Regards Thomas To Unsubscribe: send mail to [EMAIL PROTECT

question: delay of a context - switch

Hi Dose anyone know how long a the kernel is busy with context switching (beetween two processes) ? Has anyone tested this yet? I estimate of about 7 usec duration for that, (on a Pentium 400) but I think that's to long. Regards Thomas To Unsubscribe: send mail to [EMAIL PROTECTED] w

how to catch a wildrunning pointer

Hi My Problem: Within a kernel timeout routine I allocate memory and fill it with data. After a while I lock at this data again and realize that it it was modifyted (but not by me). How can I set a kernel mode watch point to that data to see which function change the data. Any Ideas Rega

Re: how to catch a wildrunning pointer

Alfred Perlstein <[EMAIL PROTECTED]> on 28.01.2000 11:49:34 To: Thomas Klein/Aachen/Utimaco/DE@utimaco cc: [EMAIL PROTECTED] Subject: Re: how to catch a wildrunning pointer > > > > Hi > > > > My Problem: > > Within a kernel timeout routin