Date: Wed, 26 Nov 2008 17:32:44 +0800 From: "Archimedes Gaviola" <archimedes.gaviola@gmail.com> To: ivoras@freebsd.org, "John Baldwin" <jhb@freebsd.org> Cc: freebsd-smp@freebsd.org Subject: Re: CPU affinity with ULE scheduler Message-ID: <42e3d810811260132l53027184s102e8a5e3b70dfb2@mail.gmail.com> In-Reply-To: <200811171609.54527.jhb@freebsd.org> References: <42e3d810811100033w172e90dbl209ecbab640cc24f@mail.gmail.com> <42e3d810811170311uddc77daj176bc285722a0c8@mail.gmail.com> <42e3d810811170336rf0a0357sf32035e8bd1489e9@mail.gmail.com> <200811171609.54527.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> In both cases the code path a packet must go through is very similar: it > has to be received, then processed through firewalls and network stack > code, then delivered to application(s), so it's a serial process. There > are things that could be better parallelized in the stack and people are > working on them, but they will not be finished any time soon. Ah okay so the project is moving towards network stack parallelism. What is the benefit of parallelized network stack in comparison to the current serialized network stack? Is there any known issues with serialized network stack dealing with multiple CPUs? If it has, in what aspect, components or subsystem of the operating system? With network stack parallelism, what are the necessary changes of the operating system? How should be the network processing be optimized with parallelized network stack? I have gone through a technical paper in the Internet about evaluation on network stack parallelism strategies for modern operating system http://www.cs.rice.edu/CS/Architecture/docs/willmann-usenix06.pdf which described about approaches in implementing parallelized network stack in which also described FreeBSD were used as the prototype of the different approaches, from here I want to know what approach does FreeBSD is implementing, is it message-based parallelism or connection-based parallelism? Thanks, Archimedes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42e3d810811260132l53027184s102e8a5e3b70dfb2>