Date: Tue, 31 Oct 2006 13:57:54 -0500 From: Mikhail Teterin <mi+mx@aldan.algebra.com> To: "Jack Vogel" <jfvogel@gmail.com> Cc: stable@freebsd.org, re@freebsd.org, Mikhail Teterin <mi+kde@aldan.algebra.com> Subject: Re: new em-driver still broken Message-ID: <200610311357.55373.mi%2Bmx@aldan.algebra.com> In-Reply-To: <2a41acea0610311049n1a8d7f92lef3cdb14cbfef7a3@mail.gmail.com> References: <200610282112.k9SLC0cC024602@corbulon.video-collage.com> <200610311307.27063.mi%2Bmx@aldan.algebra.com> <2a41acea0610311049n1a8d7f92lef3cdb14cbfef7a3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
вівторок 31 жовтень 2006 13:49, Jack Vogel написав:
> Scott's question still hasnt been answered, or if so I dont understand it.
> If everything was working why were you trying to turn on polling?
Because it was working poorly -- over 50% of the (combined) CPU time was spent
in the kernel ("sys") instead of on compressing the data ("user").
Polling seems to promise relief exactly for such situations, so I tried to
enable it.
> And if the machine is unreachable over the net, what is happening ON
> the machine at that point, does it emit any useful information?
Nothing -- the screen (console) is not updated. If I leave top(1) running,
I'll see INSANE amounts of CPU-time (1300% each, for example) getting
attributed to the compressing programs -- after that top stops refreshing.
Hitting a key (even Shift) on the console's keyboard wakes everything up for
some time, and traffic resumes -- only to stall again a minute or so later...
-mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610311357.55373.mi%2Bmx>