From owner-freebsd-net@FreeBSD.ORG Tue Nov 1 07:54:49 2011 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 D8A9C106566C for ; Tue, 1 Nov 2011 07:54:49 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 972118FC15 for ; Tue, 1 Nov 2011 07:54:49 +0000 (UTC) Received: by vws11 with SMTP id 11so399039vws.13 for ; Tue, 01 Nov 2011 00:54:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9sTmign04JMVVUHNlqU+GuUoYHrCjInFvPRzgmmqHGU=; b=jfZGACOOY4crRZcWWarNajbw0FhxPYNZREVQ5gWrnpsdD+eIMsofJRNCWfH+lh8Z2L 8Dz0AbX3dXXVwUym9CE6SfWp0w++laUvy/mxdwEDs40dPHnxTMQvHTEXCSiaAylbtdK0 RKRnVFXYtec7l9H7F8e8+Q2fyVtNulk76mTYs= MIME-Version: 1.0 Received: by 10.52.100.70 with SMTP id ew6mr7379427vdb.49.1320134088810; Tue, 01 Nov 2011 00:54:48 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.164.101 with HTTP; Tue, 1 Nov 2011 00:54:48 -0700 (PDT) In-Reply-To: <20111101015746.GA96508@nat.myhome> References: <20111101015746.GA96508@nat.myhome> Date: Tue, 1 Nov 2011 00:54:48 -0700 X-Google-Sender-Auth: CKXm_v5Jp4hA5RK9gTOklgOOHD0 Message-ID: From: Adrian Chadd To: "Paul A. Procacci" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: Re: [High Interrupt Count] Networking Difficulties 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: Tue, 01 Nov 2011 07:54:49 -0000 Hi, I'd suggest starting to dig for datasheets or alternative open source drivers (eg Linux) that exposes what the NIC can do with interrupts (eg interrupt coalescing.) I'd also suggest using hwpmc and doing a spot of profiling to find out where your CPU is being spent. Anything else is conjecture. :) adrian