Le 2019-06-05 12:06, Mark Kettenis a écrit :
Date: Wed, 5 Jun 2019 10:16:25 +0200
From: Sebastien Marie
Hi,
I would like to have feedback and testing on this diff. The initial
work
was done by ian@.
Don't forget to run "make syscalls" in sys/kern when building your own
kernel with this
> Date: Wed, 5 Jun 2019 10:16:25 +0200
> From: Sebastien Marie
>
> Hi,
>
> I would like to have feedback and testing on this diff. The initial work
> was done by ian@.
Don't forget to run "make syscalls" in sys/kern when building your own
kernel with this diff!
> It unlocks read(2) and
Hi,
I would like to have feedback and testing on this diff. The initial work
was done by ian@.
It unlocks read(2) and write(2) families, and push the KERNEL_LOCK
deeper in the code path. With it, read(2) and write(2) on socket will be
KERNEL_LOCK-free.
read(2) and write(2) are file type
