> Date: Sat, 12 Sep 2015 14:38:05 +0200 (CEST)
> From: Mark Kettenis
>
> Since interrupt handlers are running asynchronously it is difficult to
> make sure that one isn't running on another cpu while you're frobbing
> data structures that you share with it. This is an issue for example
> in our
Since interrupt handlers are running asynchronously it is difficult to
make sure that one isn't running on another cpu while you're frobbing
data structures that you share with it. This is an issue for example
in our network drivers, where we want to clean up the rings when we
bring the interface