[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070222.054127.104035694.davem@davemloft.net>
Date: Thu, 22 Feb 2007 05:41:27 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: johnpol@....mipt.ru
Cc: arjan@...radead.org, mingo@...e.hu, drepper@...hat.com,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
hch@...radead.org, akpm@....com.au, alan@...rguk.ukuu.org.uk,
zach.brown@...cle.com, suparna@...ibm.com, davidel@...ilserver.org,
jens.axboe@...cle.com, tglx@...utronix.de
Subject: Re: [patch 00/13] Syslets, "Threadlets", generic AIO support, v3
From: Evgeniy Polyakov <johnpol@....mipt.ru>
Date: Thu, 22 Feb 2007 15:39:30 +0300
> It does not matter - even with threads cost of having thousands of
> threads is _too_ expensive. So, IMO, it is wrong to have to create
> 20k threads for the simple web server which only sends one index page to
> 80k connections with 4k connections per seconds rate.
>
> Just have that example in mind - more than 20k blocks in 80k connections
> over gigabit lan, and it is likely optimistic result, when designing new
> type of AIO.
I totally agree with Evgeniy on these points.
Using things like syslets and threadlets for networking I/O
is not a very good idea. Blocking is more the norm than the
exception for networking I/O.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists