> >> It seems that there is substantial overhead just scanning interfaces for
> >> some routine maintenance...is there any hope of alleviating this deboggle?
> >
> >Probably. Without some idea of what's actually happening, though, it's a
> >little hard to point a finger and say "look here".
> >
> >A profiling dump of the system when idle would be very illuminating, as
> >it'd give you a good idea of what's actually going on to use so much CPU
>
> How do I do this in 4.1? I have a test bed set up that demonstrates the
> problem.
Config your kernel with '-pg', build and install. (See config(8))
Low-resolution profiling should be fine.
Boot the new kernel, and when it's running use kgmon to grab a profiling
dump for, say, 30 seconds. Then use gprof to translate the dump into
readable output; at this point the flat profile is a good place to start
to get a feel for where the code is busiest.
Hope this helps.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
