From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-fx0-f43.google.com (mail-fx0-f43.google.com [209.85.161.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id D9DAD2021FA for ; Sat, 5 Nov 2011 04:31:19 -0700 (PDT) Received: by faat9 with SMTP id t9so6289395faa.16 for ; Sat, 05 Nov 2011 04:31:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=KNtn+P8FCgYpM1BjwNF4HBKCXg1cU/HhWjr4xxoCCpw=; b=ucZbVKFlb2UP6u28bPb0qi91UFR3XxB17Yt1YKtq5HqOWCtkd9xJrQWEZT9LP5a/l2 /Wv3LakmWwWM2S7lJeVJMWUX90UNVirxIxwaceK0KL0geLpjtRpw9sGRQfRgGxxBXHDU VaipbU300H8unurydHLopNyKkTv3wKa1GY/n8= Received: by 10.152.105.83 with SMTP id gk19mr2579916lab.30.1320492677143; Sat, 05 Nov 2011 04:31:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.152.41.234 with HTTP; Sat, 5 Nov 2011 04:30:36 -0700 (PDT) In-Reply-To: <20111019172314.BA1D8800037@ip-64-139-1-69.sjc.megapath.net> References: <20111019095244.27354f74@nehalam.linuxnetplumber.net> <20111019172314.BA1D8800037@ip-64-139-1-69.sjc.megapath.net> From: =?UTF-8?Q?Petri_Rosenstr=C3=B6m?= Date: Sat, 5 Nov 2011 13:30:36 +0200 Message-ID: Subject: Re: PF_ring and friends: Options for making Linux suck less when capturing packets To: bloat-devel@lists.bufferbloat.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2011 11:31:20 -0000 Hi, I tried something like this with a wndr3800. I connected a usb powered hdd (didn't test for speed, but if memory serves it's about 20megabytes). Test 1. Send some small (40 bytes) packages to the route (internal network -> router (100 pkts/s)) run tcpdump -i eth1 -s 200 -w /some/usb/hdd.cap Result 1. It fills about 20kb/s of the memory. The CPU usage is about 100% from the s= tart. Test 2. Send some small (40 bytes) packages to the route (internal network -> router (20 pkts/s)) run tcpdump -i eth1 -s 200 -w /some/usb/hdd.cap Result 2. CPU usage about 80%. No noticeable memory consumption. And of course if skipping the -s option from tcpdump there are no issues with these network loads. Best regards Petri Rosenstr=C3=B6m