Re: [PATCH v3] net: dccp: Add SIOCOUTQ IOCTL support (send buffer fill)

2020-06-03 Thread Richard Siegfried
> > net-next is CLOSED > Okay, I will resend in next merge window signature.asc Description: OpenPGP digital signature

Re: [PATCH net-next 0/3] A own subdirectory for shared TCP code

2017-10-05 Thread Richard Siegfried
On 04/10/17 22:27, Andrew Lunn wrote: > Hi Richard > > It is generally unwanted. > > Have you tried back porting patches when the directory structure has > changed? Files have moved around? It makes it a lot harder to > do. Meaning patches are going to be back ported less often. Fixes > which cou

Re: [PATCH net-next 0/3] A own subdirectory for shared TCP code

2017-10-04 Thread Richard Siegfried
On 04/10/17 01:03, David Miller wrote: > As someone who has to do backports regularly to -stable, there is no way > I am applying this. > > Sorry. Okay, I see. Is grouping files into subdirectories something generally unwanted/unlikely to be applied or is this specific to TCP / networking? Becau

Re: [PATCH net-next 3/3] Move shared tcp code to net/ipv4v6shared

2017-10-04 Thread Richard Siegfried
On 04/10/17 03:32, Stephen Hemminger wrote: > The name ipv4v6_shared is longer than it needs to be maybe ip or ip_common Well ip_common sounds nice. But I don't fully understand what this means for the current situation. I could do a v2, but would that make any sense since Dave and Eric already sa

Paper: A Comparison of TCP Implementations, Linux vs. lwIP

2017-05-18 Thread Richard Siegfried
Hello, Some months ago I wrote a paper on a Comparison of TCP Implementations. (Features, Code Quality, Data Structures, etc.) https://github.com/richi235/A-Comparison-of-TCP-Implementations It's finished and the corresponding exam successfully passed. But I thought perhaps this could be interes