From: Eric Dumazet <eric.dumazet@gmail.com>
To: Erik Hugne <erik.hugne@ericsson.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jon Maloy <jon.maloy@ericsson.com>,
"ying.xue@windriver.com" <ying.xue@windriver.com>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>
Subject: Re: [PATCH] tipc: flow control should not account for sk_rcvbuf
Date: Thu, 04 Oct 2012 15:55:13 +0200 [thread overview]
Message-ID: <1349358913.16011.59.camel@edumazet-glaptop> (raw)
In-Reply-To: <506D7D24.3070601@ericsson.com>
On Thu, 2012-10-04 at 14:12 +0200, Erik Hugne wrote:
> > And this limit is tested _before_ queueing to backlog if socket is owned
> > by the user ?
> >
> > You'll have to demonstrate this in the changelog.
> >
> > Again, I dont think this patch is safe, we need an explicit limit.
> You're right Eric..
>
> Another way of solving it is to increase the default sk_rcvbuf size to
> (TIPC_FLOW_CONTROL_WIN * 2 * TIPC_MAX_USER_MSG_SIZE)
> at socket creation.
>
> Do you think that would be acceptable?
>
If its a tipc constant, you also could use
if (sk_add_backlog(sk, buf,
TIPC_FLOW_CONTROL_WIN * 2 * TIPC_MAX_USER_MSG_SIZE))
no ?
But yes, a protocol is allowed to change sk_rcvbuf value (its done for
TCP for example, with a limit to tcp_rmem[2] (between 4 and 6 Mbytes)
next prev parent reply other threads:[~2012-10-04 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 9:14 [PATCH] tipc: flow control should not account for sk_rcvbuf erik.hugne
2012-10-04 9:21 ` Eric Dumazet
2012-10-04 9:59 ` Erik Hugne
2012-10-04 10:26 ` Eric Dumazet
2012-10-04 12:12 ` Erik Hugne
2012-10-04 13:55 ` Eric Dumazet [this message]
2012-10-04 15:00 ` [PATCH v2] tipc: prevent dropped connections due to rcvbuf overflow erik.hugne
2012-10-04 19:55 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1349358913.16011.59.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=erik.hugne@ericsson.com \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=ying.xue@windriver.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox