From owner-freebsd-net@FreeBSD.ORG Wed Aug 7 20:48:35 2013 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id D049AA17; Wed, 7 Aug 2013 20:48:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 15E3E287A; Wed, 7 Aug 2013 20:48:34 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id j13so8822wgh.1 for ; Wed, 07 Aug 2013 13:48:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=PT5MUtyS8orVKPzlULFz8/3CO5Me/u1ydKaZgPTklCY=; b=HJWK7CkhBUKNuk9x18viY77YS7agDZUV4hPx+kRllqw3/FWuq12Sr0a0wf5GUWaA/O m9dAb3S79WvaqxsdsagqYIqbIq9qKkHplqXf0j2p5HrazcoDksn+YLGOI/Po8+I5jshj qjUeEPGjtFUip4eDH3z8oweAQUFEIy8rd3zHDQgQscg81XeEicEUTALx36hfPmsCUJ0R BNXMUlD+0IIZkd8tMfz/MjVXy1UdebBtSqAxXvX89Qi9MjYuE+/2L860LBXnl4Ja/6tv Ge27RE+413QzJZkhYnImzi+ZYHLoIHW7I1Typ0VxkeHct7RrPT4YQGki9nJczbv0NlTc cmXA== MIME-Version: 1.0 X-Received: by 10.180.160.165 with SMTP id xl5mr3242130wib.46.1375908513364; Wed, 07 Aug 2013 13:48:33 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.116.136 with HTTP; Wed, 7 Aug 2013 13:48:33 -0700 (PDT) In-Reply-To: References: <20130805215319.GA43271@onelab2.iet.unipi.it> <201308070326.r773QCLD035541@mail.karels.net> <5202A74E.4060602@freebsd.org> Date: Wed, 7 Aug 2013 13:48:33 -0700 X-Google-Sender-Auth: 9S3rtyi_XfEeWs8jEZE9kbTR8F8 Message-ID: Subject: Re: [net] protecting interfaces from races between control and data ? From: Adrian Chadd To: Scott Long Content-Type: text/plain; charset=ISO-8859-1 Cc: Andre Oppermann , mike@karels.net, Bryan Venteicher , Navdeep Parhar , net@freebsd.org, Giuseppe Lettieri , Luigi Rizzo 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: Wed, 07 Aug 2013 20:48:35 -0000 On 7 August 2013 13:08, Scott Long wrote: > An even rore relevant difference is that taskqueues have a much stronger > management API. Ithreads can only be scheduled by generating a hardware interrupt, > can only be drained by calling bus_teardown_intr(), and cannot be paused. Taskqueues > give you direct access to this control. It would be really nice if we had a software method to trigger an ithread to run, like a software interrupt. It would also be nice to pin taskqueues to CPUs, we can do with ithreads at the moment. -adrian