From owner-freebsd-net@FreeBSD.ORG Fri Mar 15 14:48:28 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0B1003DC for ; Fri, 15 Mar 2013 14:48:28 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 567A66E7 for ; Fri, 15 Mar 2013 14:48:27 +0000 (UTC) Received: (qmail 68610 invoked from network); 15 Mar 2013 16:00:27 -0000 Received: from c00l3r.networx.ch (HELO [127.0.0.1]) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 15 Mar 2013 16:00:27 -0000 Message-ID: <514334B6.9080001@freebsd.org> Date: Fri, 15 Mar 2013 15:48:22 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: John Baldwin Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST References: <201303141500.r2EF01EQ079753@freefall.freebsd.org> <201303150957.26192.jhb@freebsd.org> In-Reply-To: <201303150957.26192.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, Ryan Stone X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 14:48:28 -0000 On 15.03.2013 14:57, John Baldwin wrote: > On Thursday, March 14, 2013 5:59:44 pm Ryan Stone wrote: >> What's the benefit in having a both an interrupt thread and task that >> performs the same function? It seems to me that having two threads that do >> the same job is what is making this so complicated. > > Yes, yes it is. I have a branch that has changes to interrupt threads where > you can have an interrupt handler reschedule itself. That prevents this class > of problems as the handler always runs in the interrupt thread. > > I really should get that patch into HEAD someday. I've posted it to arch@ > twice now I think. :( It also fixes interrupt filters to really work properly > and be on by default. Do you have a link to that patch? -- Andre