[lkml]   [2018]   [Jul]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH net-next 1/2] tcp: call tcp_drop() in tcp collapse
On Sat, Jul 28, 2018 at 11:38 AM, Eric Dumazet <> wrote:
> On Fri, Jul 27, 2018 at 8:35 PM Yafang Shao <> wrote:
>> So what about LINUX_MIB_TCPOFOMERGE ?
>> Regarding LINUX_MIB_TCPOFOMERGE, a skb is already covered by another
>> skb, is that dropping the packet or simply lowering the memory
>> overhead ?
> What do you think ?
> If you receive two times the same payload, don't you have to drop one
> of the duplicate ?
> There is a a big difference between the two cases.

If the drop caused some data lost (which may then cause retransmition
or something), then this is a really DROP.
While if the drop won't cause any data lost, meaning it is a
non-harmful behavior, I think it should not be defined as DROP.
This is my suggestion anyway.


 \ /
  Last update: 2018-07-28 09:44    [W:0.067 / U:0.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site