Re: socket splicing without kernel lock

2019-07-04 Thread Claudio Jeker
On Thu, Jul 04, 2019 at 01:16:53PM +0200, Alexander Bluhm wrote: > On Thu, Jul 04, 2019 at 10:47:22AM +0200, Claudio Jeker wrote: > > Would it be possible to use some #defined flags here instead of 1,2,3? > > Maybe use FREAD/FWRITE or define something new. > > Makes code longer, but more readable.

Re: socket splicing without kernel lock

2019-07-04 Thread Alexander Bluhm
On Thu, Jul 04, 2019 at 10:47:22AM +0200, Claudio Jeker wrote: > Would it be possible to use some #defined flags here instead of 1,2,3? > Maybe use FREAD/FWRITE or define something new. Makes code longer, but more readable. ok? bluhm Index: sys/kern/uipc_socket.c ===

Re: socket splicing without kernel lock

2019-07-04 Thread Claudio Jeker
On Wed, Jul 03, 2019 at 11:49:51PM +0200, Alexander Bluhm wrote: > Hi, > > I would like to remove a useless kernel lock during socket splicing. > > We have a socket "so" that splices data to socket "sosp". Everytime > when space in sosp gets available, we add a task to move data from > so to sos

socket splicing without kernel lock

2019-07-03 Thread Alexander Bluhm
Hi, I would like to remove a useless kernel lock during socket splicing. We have a socket "so" that splices data to socket "sosp". Everytime when space in sosp gets available, we add a task to move data from so to sosp. Additionally we call sowakeup() from sowwakeup(). I have added this as it