From 0ea5fc66924303d1bf73ba283a383e2aadee02f2 Mon Sep 17 00:00:00 2001 From: neodarz Date: Sat, 11 Aug 2018 20:21:34 +0200 Subject: Initial commit --- pipermail/nel/2001-February/000289.html | 106 ++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 pipermail/nel/2001-February/000289.html (limited to 'pipermail/nel/2001-February/000289.html') diff --git a/pipermail/nel/2001-February/000289.html b/pipermail/nel/2001-February/000289.html new file mode 100644 index 00000000..cdd60872 --- /dev/null +++ b/pipermail/nel/2001-February/000289.html @@ -0,0 +1,106 @@ + + + + [Nel] NeL Network Engine + + + + + + +

[Nel] NeL Network Engine

+ Vianney Lecroart + lecroart@nevrax.com
+ Wed, 28 Feb 2001 10:07:19 +0100 +

+
+ +
Hello,
+
+In fact, we don't want to know the theorical limit. we know that we can
+change this value in the kernel sources and recompile it.
+
+What we don't know is the thread number limit after what the system uses too
+much CPU. In the linuxthread faq, they
+said that an application should not create more than 100 thread. In this
+case, we have to forget the solution where each
+socket is on a thread and use a blocked receive(). The problem is that
+select() is quite slow and if we have only 100 thread,
+each thread needs to manage, with a select(), around 50 players and we ll
+lost lot of time to create the array for the select()
+and check who have wakeup the select().
+
+Vianney Lecroart
+---
+lead network programmer / nevrax.com
+icq#: 6870415
+homepage: http://ace.planet-d.net
+www.geekcode.com: GCS/E d- s+++: a-- C+++$ UL++ P- L+++>+$ E+>- W++ N+ o? K-
+w++$ O- M- V- PS- PE? Y PGP t 5? X+ R- tv++ b- DI D+ G e++ h+ r-- y?
+
+----- Original Message -----
+From: "Thierry Mallard" <thierry@mallard.com>
+To: <nel@nevrax.org>
+Sent: Wednesday, February 28, 2001 8:31 AM
+Subject: Re: [Nel] NeL Network Engine
+
+
+> On Mon, Feb 26, 2001 at 05:49:39PM +0100, Bernard Hugueney wrote:
+> > [ Linux and threads ]
+> > Well, I'm as far as possible from a threads expert, but I think that
+> > what makes LinuxThreads special is that they are system threads (vs user
+> > threads) maybe heavier, but making use of SMP, so basically, I think
+> > the max nb of threads is very much system dependand (SMP?).
+>
+> In Linux 2.4.x, you may configure the maximum threads with
+> /proc/sys/kernel/threads-max, if i remember correctly.
+>
+> But the default value (4096) is still much more that what the default
+kernel
+> can really handle nicely, as is it said in some other posts. We'll have to
+> look deeper into this...
+>
+>
+> Shaman
+>
+> --
+> Thierry Mallard              |
+> GnuPG key on wwwkeys.pgp.net |
+> key 0xA3D021CB               |
+> http://thierry.mallard.com   |
+>
+> _______________________________________________
+> Nel mailing list
+> Nel@nevrax.org
+> http://www.nevrax.org/mailman/listinfo.cgi/nel
+
+
+
+ + + + + +
+

+ -- cgit v1.2.1