From owner-freebsd-net@FreeBSD.ORG Sun May 4 23:07:50 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 39B93106566C for ; Sun, 4 May 2008 23:07:50 +0000 (UTC) (envelope-from oleksandr@samoylyk.sumy.ua) Received: from mail.telesweet.net (news.telesweet.net [194.110.252.16]) by mx1.freebsd.org (Postfix) with ESMTP id DD4998FC17 for ; Sun, 4 May 2008 23:07:49 +0000 (UTC) (envelope-from oleksandr@samoylyk.sumy.ua) Received: from localhost (localhost [127.0.0.1]) by mail.telesweet.net (Postfix) with ESMTP id 0E680C0F4 for ; Mon, 5 May 2008 02:07:47 +0300 (EEST) X-Virus-Scanned: by Telesweet Mail Virus Scanner X-Spam-Flag: NO X-Spam-Score: 0.141 X-Spam-Level: X-Spam-Status: No, score=0.141 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1.44, MISSING_HEADERS=1.581] Received: from [10.0.0.109] (pigeon-work.telesweet [10.0.0.109]) by mail.telesweet.net (Postfix) with ESMTP id 76322BF09 for ; Mon, 5 May 2008 02:07:46 +0300 (EEST) Message-ID: <481E41C2.6020906@samoylyk.sumy.ua> Date: Mon, 05 May 2008 02:07:46 +0300 From: Oleksandr Samoylyk User-Agent: Thunderbird 2.0.0.12 (X11/20080227) MIME-Version: 1.0 CC: freebsd-net@freebsd.org References: <481C84B7.6020205@samoylyk.sumy.ua> <481E338D.6040706@samoylyk.sumy.ua> <2a41acea0805041529j5d4dd2f7x5e07a8d6d2eb89b6@mail.gmail.com> In-Reply-To: <2a41acea0805041529j5d4dd2f7x5e07a8d6d2eb89b6@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Troubles with em on FreeBSD 7 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, 04 May 2008 23:07:50 -0000 Jack Vogel wrote: > You are running out of RX side resources, did you say this > was UDP? I'm guessing upping your mbuf pool at least, I > can't think of something in driver-wise that would help. > > If you have this same load going into a different nic, or > different os (like say Linux) can it manage? Linux (latest 2.6.24, e1000 with NAPI) on the same hardware with same same tasks having been successfully coped with this load. I just wanted to move to FreeBSD in order to use mpd5 pptp-server with ng_car. I tried different (and new) Intel PRO 1000 NICs (PCI & PCI Express), but all the same. I'm trying to share load with separate adaptors (3 for LAN with deterrent IPs) and one for external interface (which nearly always eates much less CPU time). Vladimir Ivanov, the developer of SMPable version of EM driver, made a guess that this could be a problem with ng_* staff. I've: # kldstat Id Refs Address Size Name 1 13 0xffffffff80100000 760c78 kernel 2 1 0xffffffffae3bb000 8c73 ipfw.ko 3 1 0xffffffffae3ec000 19ba ng_socket.ko 4 10 0xffffffffae3ee000 8f14 netgraph.ko 7 1 0xffffffffae44f000 a9e ng_tee.ko 8 1 0xffffffffae450000 1a22 ng_pptpgre.ko 9 1 0xffffffffae452000 202a ng_ksocket.ko 10 1 0xffffffffae66c000 13a6 ng_iface.ko 11 1 0xffffffffae66e000 459e ng_ppp.ko 12 1 0xffffffffae678000 9e2 ng_tcpmss.ko 13 1 0xffffffffae45a000 1b24 ng_bpf.ko 14 1 0xffffffffae45c000 13be ng_car.ko 15 1 0xffffffffae4cd000 1ea4 ng_vjc.ko and I couple of ipfw rules (in order not to pass local traffic through the pptp-tunnels): deny ip from any to 10.0.0.0/8 via ng* deny ip from any to 172.16.0.0/12 via ng* deny ip from any to 192.168.0.0/16 via ng* deny ip from any to 224.0.0.0/3 via ng* deny ip from any to 169.254.0.0/16 via ng* Nothing less, nothing more :) -- Oleksandr Samoylyk OVS-RIPE