From owner-freebsd-net@FreeBSD.ORG Mon May 5 20:15:03 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 828CF106566C for ; Mon, 5 May 2008 20:15:03 +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 041E68FC27 for ; Mon, 5 May 2008 20:15:02 +0000 (UTC) (envelope-from oleksandr@samoylyk.sumy.ua) Received: from localhost (localhost [127.0.0.1]) by mail.telesweet.net (Postfix) with ESMTP id 4525C1005D for ; Mon, 5 May 2008 23:14:59 +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 DCE2D1005C for ; Mon, 5 May 2008 23:14:30 +0300 (EEST) Message-ID: <481F6AA8.60002@samoylyk.sumy.ua> Date: Mon, 05 May 2008 23:14:32 +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> <2a41acea0805041532le60cc9cybf22887e9fdcb3f9@mail.gmail.com> <481EEE34.7060804@samoylyk.sumy.ua> In-Reply-To: <481EEE34.7060804@samoylyk.sumy.ua> 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: Mon, 05 May 2008 20:15:03 -0000 Oleksandr Samoylyk wrote: > Jack Vogel wrote: >> Oh, I just had a thought, increase the RX processing limit, >> that only allows you to process 100 packets in one pass. >> >> First change it to 250 and see what it does, you might >> also set it to -1 which will allow you to process til you >> drain the ring, the risk is that you cause other problems >> by doing that, but heck at this point anything is worth >> trying, right? >> > > Nothing has helped. :( > > I need to unplug and plug in again patch cords each time when my CPUs > with emX go 100% in order to keep my server alive with a descent pings. > > I mentioned that "100%: emX taskq" occurs only on that interfaces where > GRE packets are being processed. > > External interface to Internet feels great. Pings are <0ms and load is > 9.57% with 14kpps (input/output). > > Maybe interesting: > According to kgmon: > % cumulative self self total > time seconds seconds calls ms/call ms/call name > 39.9 93.10 93.10 1643247 0.06 0.07 rip_input [10] > > Is it em related or mpd related or something else? > > Back to releng_6? Not sure though. :( > Now I'm on 6.3-STABLE: last pid: 31566; load averages: 7.61, 7.25, 7.07 up 0+01:34:00 22:30:05 82 processes: 10 running, 58 sleeping, 14 waiting CPU states: 0.2% user, 0.0% nice, 52.1% system, 47.8% interrupt, 0.0% idle Mem: 63M Active, 10M Inact, 152M Wired, 8K Cache, 35M Buf, 1752M Free Swap: 4011M Total, 4011M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 12 root 1 -44 -163 0K 8K WAIT 0 42:43 93.60% swi1: net 24 root 1 43 0 0K 8K CPU0 0 29:50 48.34% em0_rx_kthread_1 23 root 1 43 0 0K 8K RUN 0 29:50 46.78% em0_rx_kthread_0 28 root 1 43 0 0K 8K RORDER 1 3:30 2.25% em1_rx_kthread_0 29 root 1 43 0 0K 8K RUN 0 3:30 2.15% em1_rx_kthread_1 10 root 1 171 52 0K 8K RUN 1 11:22 0.00% idle: cpu1 11 root 1 171 52 0K 8K RUN 0 9:01 0.00% idle: cpu0 The results aren't good as well. -- Oleksandr Samoylyk OVS-RIPE