From owner-freebsd-stable@FreeBSD.ORG Sat Oct 21 17:34:10 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A837516A407; Sat, 21 Oct 2006 17:34:10 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E11A643D9E; Sat, 21 Oct 2006 17:34:08 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id k9LHXwsi078188 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Oct 2006 21:33:58 +0400 (MSD) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id k9LHXwEG078187; Sat, 21 Oct 2006 21:33:58 +0400 (MSD) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 21 Oct 2006 21:33:58 +0400 From: Gleb Smirnoff To: Mikhail Teterin Message-ID: <20061021173358.GC75694@cell.sick.ru> Mail-Followup-To: Gleb Smirnoff , Mikhail Teterin , freebsd-stable@freebsd.org, freebsd-net@freebsd.org References: <200610211300.09476@aldan> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200610211300.09476@aldan> User-Agent: Mutt/1.5.6i Cc: freebsd-net@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: em network issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2006 17:34:10 -0000 On Sat, Oct 21, 2006 at 01:00:08PM -0400, Mikhail Teterin wrote: M> = I'd appreciate if people who are observing the problem will report M> = whether adding DEVICE_POLLING option to kernel config helps them M> = or not. This will help to tell whether the problem is in the above M> = quote or in the import of new versions from vendor. M> M> I tried this yesterday -- before writing to net@. I saw the "system" component M> of the total load being rather high and then enabled polling. M> M> Again, I did not wait long enough to check, whether the system will cease M> communicating completely before enabling polling on em, but the "system" load M> was shooting way up upon starting my backup procedure even when I switched to M> DEVICE_POLLING-using kernel. We aren't currently speaking about performance, we need to know whether kernel with DEVICE_POLLING option makes NIC work stable. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE