New Feature or Strange bug

Христо Чернев <[email protected]>
Newsgroups gmane.network.tux
Message-ID <[email protected]>
I 've been using TUX as static http server from half year. It is used in
production on Dual Xeon box ( hyperthreading enabled).
The kernel is compiled by me Redhad source - 2.4.18-18.7.xcustom SMP.
All is fine ( except loging, and tuxstat segfault but it is fine by me ).
Now I am trying to setup another box ( same hardware) and I compiled the last RH
kernel 2.4.20-20.7custom SMP.
When I start TUX on the new machine and look the proccesses I see:
root     30594  0.0  0.0  1592  644 pts/0    S    15:27   0:00 [TUX date]
root     30595  0.0  0.0     0    0 ?        SW   15:27   0:00 [TUX logger]
root     30596  0.0  0.0  1600  652 ?        S    15:27   0:00 [TUX manager]
nobody   30597  0.0  0.0  1600  652 ?        S    15:27   0:00 [TUX worker 0]
nobody   30598  0.0  0.0  1600  652 ?        S    15:27   0:00 [async IO 0/1]
nobody   30599  0.0  0.0  1600  652 ?        S    15:27   0:00 [async IO 0/2]
....
nobody   30628  0.0  0.0  1600  652 ?        S    15:27   0:00 [async IO 0/31]
nobody   30629  0.0  0.0  1600  652 ?        S    15:27   0:00 [async IO 0/32]
(There weren't such processes on my old TUX box. There were only [TUX worker
x].)
What is this "async IO 0/x" ? Is there something to worry about?

-------------
Hristo Chernev<a href='http://mail.bg/ads/adclick.php?bannerid=860&amp;zoneid=13&amp;source=&amp;ismap=' target='_blank'><p>СТАНТЕК - http://www.stantek.com<br/>
компютри за дома и офиса,<br/>
коректно обслужване,<br/>
партньорство и добри цени</p></a><div id="beacon_860" style="position: absolute; left: 0px; top: 0px; visibility: hidden;"><img src='http://mail.bg/ads/adlog.php?bannerid=860&amp;clientid=273&amp;zoneid=13&amp;source=&amp;block=0&amp;capping=0&amp;cb=6e10cc54e4f929f3990f137d0d8769ab' width='0' height='0' alt='' style='width: 0px; height: 0px;'></div>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.