Re: TCP Initial Window 10 MFC

2013-08-14 Thread Lawrence Stewart
On 08/15/13 02:44, Andre Oppermann wrote: > On 14.08.2013 04:36, Lawrence Stewart wrote: >> Hi Andre, >> >> [RE team is BCCed so they're aware of this discussion] >> >> On 07/06/13 00:58, Andre Oppermann wrote: >>> Author: andre >>> Date: Fri Jul 5 14:58:24 2013 >>> New Revision: 252789 >>> URL: h

Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux)

2013-08-14 Thread Vijay Singh
Is that what FLOWTABLE does? Also we need a mechanism to record time spent at various layers in the stack. Luigi has used his own methods but we're lacking something more generic. At work we have some crude tools that use mcount information to indirectly measure costs but they are not reliable a

Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux)

2013-08-14 Thread Luigi Rizzo
On Wed, Aug 14, 2013 at 12:40:19PM -0700, Peter Wemm wrote: > On Wed, Aug 14, 2013 at 11:11 AM, Adrian Chadd wrote: > > On 14 August 2013 04:47, Lev Serebryakov wrote: > > > > > >> And we should invalidate this info on ARP/route changes, or connection > >> will be lost in such cases, am I righ

Re: TCP Initial Window 10 MFC (was: Re: svn commit: r252789 - stable/9/sys/netinet)

2013-08-14 Thread Eggert, Lars
Oh: The other interesting bit is that Chrome defaulted to telling the server to use IW32 if it had no cached value... I think Google are still heavily tweaking the mechanisms. Lars On Aug 14, 2013, at 16:46, "Eggert, Lars" wrote: > Hi, > > On Aug 14, 2013, at 10:36, Lawrence Stewart wrote:

Re: TCP Initial Window 10 MFC

2013-08-14 Thread Eggert, Lars
Hi, On Aug 14, 2013, at 17:27, Lawrence Stewart wrote: > Do you recall if they said > how many flows made up the CDF? I think "very many" - check out the audio archive or the minutes of the meeting, it should have the details. Lars signature.asc Description: Message signed with OpenPGP usin

Re: TSO and FreeBSD vs Linux

2013-08-14 Thread Kevin Oberman
On Wed, Aug 14, 2013 at 12:46 PM, Julian Elischer wrote: > On 8/14/13 3:23 PM, Lawrence Stewart wrote: > >> On 08/14/13 16:33, Julian Elischer wrote: >> >> They switched to using an initial window of 10 segments some time ago. FreeBSD starts with 3 or more recently, 10 if you're running rece

Re: TSO and FreeBSD vs Linux

2013-08-14 Thread Julian Elischer
On 8/14/13 3:23 PM, Lawrence Stewart wrote: On 08/14/13 16:33, Julian Elischer wrote: They switched to using an initial window of 10 segments some time ago. FreeBSD starts with 3 or more recently, 10 if you're running recent 9-STABLE or 10-CURRENT. I tried setting initial values as shown: n

Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux)

2013-08-14 Thread Peter Wemm
On Wed, Aug 14, 2013 at 11:11 AM, Adrian Chadd wrote: > On 14 August 2013 04:47, Lev Serebryakov wrote: > > >> And we should invalidate this info on ARP/route changes, or connection >> will be lost in such cases, am I right?.. So, on each such event code >> should look into all sockets and ch

Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux)

2013-08-14 Thread Adrian Chadd
On 14 August 2013 04:47, Lev Serebryakov wrote: > And we should invalidate this info on ARP/route changes, or connection > will be lost in such cases, am I right?.. So, on each such event code > should look into all sockets and check, if routing/ARP information is > still > valid for them.

Re: TCP Initial Window 10 MFC

2013-08-14 Thread Andre Oppermann
On 14.08.2013 04:36, Lawrence Stewart wrote: Hi Andre, [RE team is BCCed so they're aware of this discussion] On 07/06/13 00:58, Andre Oppermann wrote: Author: andre Date: Fri Jul 5 14:58:24 2013 New Revision: 252789 URL: http://svnweb.freebsd.org/changeset/base/252789 Log: MFC r242266:

Re: TSO and FreeBSD vs Linux

2013-08-14 Thread Julian Elischer
On 8/14/13 2:33 PM, Julian Elischer wrote: On 8/14/13 11:39 AM, Lawrence Stewart wrote: There's a thing controlled by ethtool called GRO (generic receive offload) which appears to be enabled by default on at least Ubuntu and I guess other Linux's too. It's responsible for aggregating ACKs and

Re: route/arp lifetime (Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux))

2013-08-14 Thread Luigi Rizzo
On Wed, Aug 14, 2013 at 05:40:28PM +0200, Marko Zec wrote: > On Wednesday 14 August 2013 14:40:24 Luigi Rizzo wrote: > > On Wed, Aug 14, 2013 at 04:15:25PM +0400, Alexander V. Chernikov wrote: ... > FWIW, apparently we already have that infrastrucure in place - if_rele() > calls if_free_internal()

Re: route/arp lifetime (Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux))

2013-08-14 Thread Marko Zec
On Wednesday 14 August 2013 14:40:24 Luigi Rizzo wrote: > On Wed, Aug 14, 2013 at 04:15:25PM +0400, Alexander V. Chernikov wrote: > > On 14.08.2013 16:05, Luigi Rizzo wrote: > > > On Wed, Aug 14, 2013 at 03:47:13PM +0400, Lev Serebryakov wrote: > > >> Hello, Luigi. > > >> You wrote 14 ?

Re: route/arp lifetime (Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux))

2013-08-14 Thread Luigi Rizzo
On Wed, Aug 14, 2013 at 05:01:05PM +0400, Alexander V. Chernikov wrote: > On 14.08.2013 16:40, Luigi Rizzo wrote: ... > >> You can save rte&arp, however doing this > >> gives you perfect chance to crash your kernel if egress interface is > >> destroyed (like vlan or ng or tun). > > I hope I learned

Updating route MTU when interface changes

2013-08-14 Thread Joe Holden
Hi guys, I noticed this some years ago but I just checked and its still there - when the mtu of an interface is changed, any routes (eg connected route) using that interface aren't updated until the interface is shut/unshut - is this by design or is it an oversight? Having to down/up remote

Re: route/arp lifetime (Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux))

2013-08-14 Thread Alexander V. Chernikov
On 14.08.2013 16:40, Luigi Rizzo wrote: On Wed, Aug 14, 2013 at 04:15:25PM +0400, Alexander V. Chernikov wrote: On 14.08.2013 16:05, Luigi Rizzo wrote: On Wed, Aug 14, 2013 at 03:47:13PM +0400, Lev Serebryakov wrote: Hello, Luigi. You wrote 14 ?? 2013 ??., 14:21:09: LR> Then the p

Re: route/arp lifetime (Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux))

2013-08-14 Thread Luigi Rizzo
On Wed, Aug 14, 2013 at 04:15:25PM +0400, Alexander V. Chernikov wrote: > On 14.08.2013 16:05, Luigi Rizzo wrote: > > On Wed, Aug 14, 2013 at 03:47:13PM +0400, Lev Serebryakov wrote: > >> Hello, Luigi. > >> You wrote 14 ?? 2013 ??., 14:21:09: > >> > >> LR> Then the problem remains that

Re: route/arp lifetime (Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux))

2013-08-14 Thread Alexander V. Chernikov
On 14.08.2013 16:05, Luigi Rizzo wrote: On Wed, Aug 14, 2013 at 03:47:13PM +0400, Lev Serebryakov wrote: Hello, Luigi. You wrote 14 ?? 2013 ??., 14:21:09: LR> Then the problem remains that we should keep a copy of route and LR> arp information in the socket instead of redoing the lo

ng_ipacct locking rework

2013-08-14 Thread Vsevolod Stakhov
Hello, I've reworked the locking model of the ng_ipacct module (ports/net-mgmt/ng_ipacct) for better parallel access support. I did the following: - convert locking from a global mutex to hash bucket level locks; - convert a mutex to rmlock (as ip accounting data is mostly read from the hash

route/arp lifetime (Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux))

2013-08-14 Thread Luigi Rizzo
On Wed, Aug 14, 2013 at 03:47:13PM +0400, Lev Serebryakov wrote: > Hello, Luigi. > You wrote 14 ?? 2013 ??., 14:21:09: > > LR> Then the problem remains that we should keep a copy of route and > LR> arp information in the socket instead of redoing the lookups on > LR> every single trans

Re: it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux)

2013-08-14 Thread Lev Serebryakov
Hello, Luigi. You wrote 14 августа 2013 г., 14:21:09: LR> Then the problem remains that we should keep a copy of route and LR> arp information in the socket instead of redoing the lookups on LR> every single transmission, as they consume some 25% of the time of LR> a sendto(), and probably even mo

it's the output, not ack coalescing (Re: TSO and FreeBSD vs Linux)

2013-08-14 Thread Luigi Rizzo
On Wed, Aug 14, 2013 at 05:23:02PM +1000, Lawrence Stewart wrote: > On 08/14/13 16:33, Julian Elischer wrote: > > On 8/14/13 11:39 AM, Lawrence Stewart wrote: > >> On 08/14/13 03:29, Julian Elischer wrote: > >>> I have been tracking down a performance embarrassment on AMAZON EC2 and > >>> have foun

telnet authentication using RADIUS

2013-08-14 Thread takCoder
hi all, I need to apply radius authentication for my remote connections. For ssh, I have no problems, as I use pam.d/sshd file to add pam_radius.so entry.. but for telnet I've faced a problem.. as I have seen, for non-SRA telnet connections, telnet authentication will be done via pam.d/login rath

Re: TCP Initial Window 10 MFC

2013-08-14 Thread Lawrence Stewart
Hi Lars, On 08/14/13 18:46, Eggert, Lars wrote: > Hi, > > On Aug 14, 2013, at 10:36, Lawrence Stewart wrote: >> I don't think this change should have been MFCed, at least not in its >> current form. > > FYI, Google's own data as presented in the HTTPBIS working group of the > recent Berlin IET

Re: TCP Initial Window 10 MFC (was: Re: svn commit: r252789 - stable/9/sys/netinet)

2013-08-14 Thread Eggert, Lars
Hi, On Aug 14, 2013, at 10:36, Lawrence Stewart wrote: > I don't think this change should have been MFCed, at least not in its > current form. FYI, Google's own data as presented in the HTTPBIS working group of the recent Berlin IETF shows that 10 is too high for ~25% of their web connections:

Fwd: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery

2013-08-14 Thread Fernando Gont
Folks, FYI. -- this is an important piece when it comes to First Hop (i.e., "local link") Security. Cheers, Fernando Original Message Subject: RFC 6980 on Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery Date: Tue, 13 Aug 2013 15:13:21 -0700 (PDT) Fro

Re: TSO and FreeBSD vs Linux

2013-08-14 Thread Lawrence Stewart
On 08/14/13 16:33, Julian Elischer wrote: > On 8/14/13 11:39 AM, Lawrence Stewart wrote: >> On 08/14/13 03:29, Julian Elischer wrote: >>> I have been tracking down a performance embarrassment on AMAZON EC2 and >>> have found it I think. >> Let us please avoid conflating performance with throughput.