[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120423.160149.1515408777176168288.davem@davemloft.net>
Date: Mon, 23 Apr 2012 16:01:49 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: rick.jones2@...com, netdev@...r.kernel.org, therbert@...gle.com,
ncardwell@...gle.com, maze@...gle.com, ycheng@...gle.com,
ilpo.jarvinen@...sinki.fi
Subject: Re: [PATCH 2/2 net-next] tcp: sk_add_backlog() is too agressive
for TCP
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Mon, 23 Apr 2012 19:23:15 +0200
> On Mon, 2012-04-23 at 10:14 -0700, Rick Jones wrote:
>
>>
>> This will increase what can be queued for arriving segments in general
>> and not for ACKs specifically yes? (A possible issue that would have
>> come-up with my previous wondering about just increasing SO_RCVBUF as
>> SO_SNDBUF was increasing). Perhaps only add sk->sk_sndbuf to the limit
>> if the arriving segment contains no data?
>
> Thats the backlog limit that we tweak here.
>
> Its not a big deal if we allow a bit more packets to come and later drop
> them if we hit the real rcvbuf limit. (ACKS wont consume space, since
> they are freed as soon as processed)
Hmmm... why don't we just acknowledge reality and special case ACKs?
If a TCP packet is dataless we should just let it go through no matter
what and with no limits. It is by definition transient and will not
get queued up into the socket past this backlog stage.
This proposed patch allows non-dataless packets to eat more space in
the backlog, thus the concern and slight pushback. And from another
perspective, having the stack process data packets which will just
get dropped when we try to attach it to the receive queue is just
wasted work.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists