> Date: Sat, 24 Jan 2015 10:47:59 +1000
> From: David Gwynne
>
> Lots of other things would have to change when that happens too. Until then
> I'll take any latency improvement I can get.
The difference is noticable?
Note that intr_disestablish() uses an atomic operation to clear bits.
That one
Lots of other things would have to change when that happens too. Until then
I'll take any latency improvement I can get.
On 24 Jan 2015 12:40 am, "Mark Kettenis" wrote:
> > Date: Fri, 23 Jan 2015 22:52:37 +1000
> > From: David Gwynne
> >
> > when a softint gets scheduled, we set a bit in the cur
> Date: Fri, 23 Jan 2015 22:52:37 +1000
> From: David Gwynne
>
> when a softint gets scheduled, we set a bit in the current cpus
> cpu_info structure. that doesnt have to be an interlocked operation
> to be locally atomic.
>
> ok?
Hmm, but it will need to be if we ever want to have the ability
softints and interlocking, sorry.
> On 23 Jan 2015, at 10:52 pm, David Gwynne wrote:
>
> when a softint gets scheduled, we set a bit in the current cpus
> cpu_info structure. that doesnt have to be an interlocked operation
> to be locally atomic.
>
> ok?
>
> Index: arch/amd64/amd64/intr.c
> ==
when a softint gets scheduled, we set a bit in the current cpus
cpu_info structure. that doesnt have to be an interlocked operation
to be locally atomic.
ok?
Index: arch/amd64/amd64/intr.c
===
RCS file: /cvs/src/sys/arch/amd64/amd64/
