there's nothing random about this file, and it upsets me whenever i see it's
name go by, because i panic thinking mg has some stupid random number
generator that hasn't been fixed yet. util.c is a better name.
(and cvs rm/add)
Index: Makefile
This diff makes the tx completion path run without the kernel lock
held. With this change, the interrupt handler will not grab the
kernel lock under normal circumstances. The diff follows the same
approach as dlg@ took with vmx(4).
The diff removes the code that tries to reclaim tx descriptors
It seems to me that the recent iwm(4)/if_setlladdr() fix applies to
more (if not all) wireless drivers since the stack keeps its own
copy of the lladdr. Does the diff below make sense?
I'd also suggest to stop abusing "ac_enaddr" or "ic_myaddr" and use
if_sadl instead. Having 3 copies of the
On Mon, Sep 28, 2015 at 01:02:24PM +0200, Martin Pieuchot wrote:
> It seems to me that the recent iwm(4)/if_setlladdr() fix applies to
> more (if not all) wireless drivers since the stack keeps its own
> copy of the lladdr. Does the diff below make sense?
>
> I'd also suggest to stop abusing
Earlier this month, kettenis identified a bug in uvm from an incompletely
reverted change. Clearing the wrong bit on a page would sometimes result in
the page queues being corrupted, and then eventually the system would crash or
panic.
This issue affects 5.7 and the forthcoming 5.8 release.
On 28.9.2015. 23:53, Mark Kettenis wrote:
> This diff makes the tx completion path run without the kernel lock
> held. With this change, the interrupt handler will not grab the
> kernel lock under normal circumstances. The diff follows the same
> approach as dlg@ took with vmx(4).
>
> The diff
