Date: Thu, 21 Jun 2007 08:26:22 -0700 From: John Polstra <jdp@polstra.com> To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org Subject: Re: in-kernel tcp server Message-ID: <467A989E.5@polstra.com> In-Reply-To: <4679D79E.5030200@elischer.org> References: <c4630b800706180227x2f1f433dr4ef55e8623062bf1@mail.gmail.com> <467787EF.9060009@elischer.org> <46797825.10900@polstra.com> <c4630b800706201239jdf09685t1574e78493492029@mail.gmail.com> <46799032.5060009@polstra.com> <c4630b800706201350p176ddadcu6b4eb341751d94e7@mail.gmail.com> <467999C9.9000402@elischer.org> <4679D081.7070600@polstra.com> <4679D79E.5030200@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Julian Elischer wrote: > but if you did find some old ksocket based code sitting around, > i'd love to try it in -current and work on the bottlenecks.. I'm sure I don't have it any more, unfortunately. It was six years old, and I just moved into a smaller house and threw out a half dozen old computers as well as my ancient backup tapes. > I'll certainly look at what I can do about the queue items. > I may make a per-cpu cache of them. That would probably help a lot. Each webserver or webclient is tied to one network interface, and I get the best performance when there is one CPU core per interface. I'm not using CPU affinity yet, but I'll probably put that in before long. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?467A989E.5>