From owner-freebsd-net@FreeBSD.ORG  Thu May  9 16:30:46 2013
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 22DFCF2F
 for <freebsd-net@freebsd.org>; Thu,  9 May 2013 16:30:46 +0000 (UTC)
 (envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [IPv6:2a03:3100:c:13::5])
 by mx1.freebsd.org (Postfix) with ESMTP id 4D88EDD
 for <freebsd-net@freebsd.org>; Thu,  9 May 2013 16:30:44 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
 by eg.sd.rdtc.ru (8.14.6/8.14.6) with ESMTP id r49GUfnh007850;
 Thu, 9 May 2013 23:30:41 +0700 (NOVT)
 (envelope-from egrosbein@rdtc.ru)
Message-ID: <518BCF2C.3080307@rdtc.ru>
Date: Thu, 09 May 2013 23:30:36 +0700
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/20130415 Thunderbird/17.0.5
MIME-Version: 1.0
To: Barney Cordoba <barney_cordoba@yahoo.com>
Subject: Re: High CPU interrupt load on intel I350T4 with igb on 8.3
References: <1368116720.51479.YahooMailClassic@web121606.mail.ne1.yahoo.com>
In-Reply-To: <1368116720.51479.YahooMailClassic@web121606.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org,
 =?UTF-8?B?IkNsw6ltZW50IEhlcm1hbm4gKG5vZGVucyki?= <nodens2099@gmail.com>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 09 May 2013 16:30:46 -0000

On 09.05.2013 23:25, Barney Cordoba wrote:

>> Network device driver is not guilty here, that's just pf's
>> contention
>> running in igb's context.
>>
>> Eugene Grosbein
> 
> They're both at play. Single threadedness aggravates subsystems that 
> have too many lock points.
> 
> It can also be "solved" with using 1 queue, because then you don't
> have 4 queues going into a single thread.

Again, the problem is within pf(4)'s global lock, not in the igb(4).