Re: [PATCH v2 net-next 0/7] net: make TCP preemptible

2016-04-30 Thread Julian Anastasov
Hello, On Fri, 29 Apr 2016, Eric Dumazet wrote: > I had corruptions issues and a dying HDD one month ago. > > I have a brand new HDD, but maybe the SSD I use for my git trees is > dying as well :( > > But I've seen this strange patterns in the past, it might be the old > text editor I

[PATCH v2 net-next 0/7] net: make TCP preemptible

2016-04-29 Thread Eric Dumazet
Most of TCP stack assumed it was running from BH handler. This is great for most things, as TCP behavior is very sensitive to scheduling artifacts. However, the prequeue and backlog processing are problematic, as they need to be flushed with BH being blocked. To cope with modern needs, TCP socke

Re: [PATCH v2 net-next 0/7] net: make TCP preemptible

2016-04-29 Thread Eric Dumazet
On Fri, 2016-04-29 at 16:39 -0400, David Miller wrote: > From: Eric Dumazet > Date: Thu, 28 Apr 2016 20:10:42 -0700 > > > Most of TCP stack assumed it was running from BH handler. > > Assuming you are respinning this to fix that stats bumping typo. > > You should really look into how that got c

Re: [PATCH v2 net-next 0/7] net: make TCP preemptible

2016-04-29 Thread David Miller
From: Eric Dumazet Date: Thu, 28 Apr 2016 20:10:42 -0700 > Most of TCP stack assumed it was running from BH handler. Assuming you are respinning this to fix that stats bumping typo. You should really look into how that got corrupted. :)

[PATCH v2 net-next 0/7] net: make TCP preemptible

2016-04-28 Thread Eric Dumazet
Most of TCP stack assumed it was running from BH handler. This is great for most things, as TCP behavior is very sensitive to scheduling artifacts. However, the prequeue and backlog processing are problematic, as they need to be flushed with BH being blocked. To cope with modern needs, TCP socke