Date: Wed, 7 Aug 2013 13:48:33 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Scott Long <scott4long@yahoo.com> Cc: Andre Oppermann <andre@freebsd.org>, mike@karels.net, Bryan Venteicher <bryanv@daemoninthecloset.org>, Navdeep Parhar <np@freebsd.org>, net@freebsd.org, Giuseppe Lettieri <g.lettieri@iet.unipi.it>, Luigi Rizzo <rizzo@iet.unipi.it> Subject: Re: [net] protecting interfaces from races between control and data ? Message-ID: <CAJ-Vmok-Z4w5iuqauOYvPKSMOKTrGi%2BWhoYx6cArChW76eh-1A@mail.gmail.com> In-Reply-To: <DBE2F2CD-02F7-4738-B4FE-446C0B45C941@yahoo.com> References: <20130805215319.GA43271@onelab2.iet.unipi.it> <201308070326.r773QCLD035541@mail.karels.net> <CA%2BhQ2%2Bi2MEKw-A=T-x1gw87P5G0g-xko-XPmE__=Cy=Airb1vg@mail.gmail.com> <5202A74E.4060602@freebsd.org> <DBE2F2CD-02F7-4738-B4FE-446C0B45C941@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7 August 2013 13:08, Scott Long <scott4long@yahoo.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmok-Z4w5iuqauOYvPKSMOKTrGi%2BWhoYx6cArChW76eh-1A>