From owner-freebsd-net@FreeBSD.ORG Sun Oct 26 13:43:02 2008 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09FDD10656A2; Sun, 26 Oct 2008 13:43:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D7BF48FC2B; Sun, 26 Oct 2008 13:43:01 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id 5216F46B0C; Sun, 26 Oct 2008 09:43:01 -0400 (EDT) Date: Sun, 26 Oct 2008 13:43:01 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kip Macy In-Reply-To: <3c1674c90810241552v5fd3e58fvf6bd43ad94558b1e@mail.gmail.com> Message-ID: References: <200810241612.04764.gizmen@blurp.pl> <3c1674c90810241552v5fd3e58fvf6bd43ad94558b1e@mail.gmail.com> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Bartosz Giza , freebsd-net@freebsd.org Subject: Re: does freebsd support so called Scalable I/O on intel NIC ? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2008 13:43:02 -0000 On Fri, 24 Oct 2008, Kip Macy wrote: > It is simply a knob to adjust on all new server network cards. You could > benefit from it on a predominantly UDP workload. I believe that tcp_input is > still sufficiently serialized that it would not make sense for TCP > workloads. In principle we can benefit on the basis that we drop the global lock fairly quickly for steady-state workloads (i.e., few SYN/FIN/RST packets), but there should be lots of contention on tcbinfo. If anyone is interested in doing some benchmarks, I have some patches that should apply fairly easily againts 8.x or 7.x as of 7.1 to move to optimistic read-locking of the global lock for steady state packets, but once in a while we have to upgrade or drop and re-acquire to get an exclusive lock when it turns out something that looked like a steady state packet did require the global lock exclusively, such as the ACK to transitioning to or from established. I've not had a chance to do much benchmarking on them, and theorize that they probably help quite a lot for lots of steady-state connections, but as connection length gets shorter the optimistic assumption becomes less true and begins to hurt performance. The long-term plan is to move to some more agressive decomposition of the tcbinfo lock, but I've not started on that yet as I'm waiting for the rwlock changes to settle, and need to evaluate the above tcbinfo rwlock patch. Robert N M Watson Computer Laboratory University of Cambridge > > -Kip > > On Fri, Oct 24, 2008 at 2:12 PM, Bartosz Giza wrote: >> Hi, >> >> i am looking for a good NIC from NIC to put on our quite busy router based >> on freebsd 6.3 (soon 7.x) >> I've found server NIC from intel and there is such a thing like scalable I/O >> on windows and linux. >> (from web page) >> >> "load balancing on multiple CPUs Increases >> performance on multi-processor systems by efficiently >> balancing network loads across CPU cores when used >> with Receive-Side Scaling from Microsoft or Scalable >> I/O on Linux*" >> >> Is such thing supported on freebsd ? >> >> And one more question. Does anybody has some data what is difference on >> desktop and server NIC from INTEL in pps or so. >> I wonder how faster could be those server NICs >> >> thanks >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >