Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Mar 2015 18:40:31 +0300
From:      Slawa Olhovchenkov <slw@zxy.spb.ru>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>
Subject:   Re: irq cpu binding
Message-ID:  <20150328154031.GA23643@zxy.spb.ru>
In-Reply-To: <CAJ-Vmo=sxtLgn1HABbWchu1Hm8kZ4Qy%2BscPeD7ezkkBzr%2BQijA@mail.gmail.com>
References:  <20150328112035.GZ23643@zxy.spb.ru> <CAJ-Vmo=sxtLgn1HABbWchu1Hm8kZ4Qy%2BscPeD7ezkkBzr%2BQijA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 28, 2015 at 08:20:08AM -0700, Adrian Chadd wrote:

> On 28 March 2015 at 04:20, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote:
> > Can someone describe how on FreeBSD/amd64 do interrupt handling?
> > Can be interrupt handler (hardware interrupt) direct dispatch to
> > specific CPU core (and only to this core)?
> > Can be all work be only on this core (ithread, device driver interrupt
> > handler, finalise)?
> 
> Yes - you can use cpuset on the interrupt to get them bound that way.
> 
> John and I are trying to make that whole process more automated and
> NUMA friendly. I'm debugging some of his work at the moment.

cpuset don't work as expected -- I see irq handling on other cpu.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150328154031.GA23643>