Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Michael Tuexen
> On 24. Apr 2020, at 23:41, Neel Chauhan  wrote:
> 
> Not OP, but would BBR work with VNET, or is that a WIP?
I would say it should work. At least, if not I would consider it a bug.
I think most testing was not done with multiple VNETs.

Best regards
Michael
> 
> I'm sorry if none of you are familiar with VNET.
> 
> -Neel
> 
> ===
> 
> https://www.neelc.org/
> BTW: Not neel@ the committer
> 
> On 2020-04-24 12:25, Michael Tuexen wrote:
>>> On 24. Apr 2020, at 21:06, Rodney W. Grimes  
>>> wrote:
 On Fri, Apr 24, 2020 at 01:31:35PM +0200, Kurt Jaeger wrote:
> Thanks. Is BBR active automatically or is there a sysctl or
> socket option to activate it ?
 net.inet.tcp.cc.available: List available congestion control algorithms
 net.inet.tcp.cc.algorithm: Default congestion control algorithm
>>> Start at:
>>> man mod_cc
>> BBR is conceptually a CC, but in FreeBSD it is NOT implemented as a CC 
>> module.
>> It is a TCP stack. You need to load it using
>> kldload tcp_bbr
>> and then either make it the default by
>> sudo sysctl net.inet.tcp.functions_default=bbr
>> or use the IPPROTO_TCP level socket option TCP_FUNCTION_BLK to set the stack
>> to BBR. The uperf test tool allows to set the TCP stack for measurements.
>> Please note that you need to compile the kernel with
>> makeoptions  WITH_EXTRA_TCP_STACKS=1
>> options  TCPHPTS
>> Best regards
>> Michael
>>> --
>>> Rod Grimes 
>>> rgri...@freebsd.org
>>> ___
>>> freebsd-current@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>> ___
>> freebsd-current@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Neel Chauhan

Not OP, but would BBR work with VNET, or is that a WIP?

I'm sorry if none of you are familiar with VNET.

-Neel

===

https://www.neelc.org/
BTW: Not neel@ the committer

On 2020-04-24 12:25, Michael Tuexen wrote:
On 24. Apr 2020, at 21:06, Rodney W. Grimes 
 wrote:



On Fri, Apr 24, 2020 at 01:31:35PM +0200, Kurt Jaeger wrote:


Thanks. Is BBR active automatically or is there a sysctl or
socket option to activate it ?


net.inet.tcp.cc.available: List available congestion control 
algorithms

net.inet.tcp.cc.algorithm: Default congestion control algorithm


Start at:
man mod_cc
BBR is conceptually a CC, but in FreeBSD it is NOT implemented as a CC 
module.

It is a TCP stack. You need to load it using
kldload tcp_bbr
and then either make it the default by
sudo sysctl net.inet.tcp.functions_default=bbr
or use the IPPROTO_TCP level socket option TCP_FUNCTION_BLK to set the 
stack
to BBR. The uperf test tool allows to set the TCP stack for 
measurements.

Please note that you need to compile the kernel with
makeoptions WITH_EXTRA_TCP_STACKS=1
options TCPHPTS

Best regards
Michael



--
Rod Grimes 
rgri...@freebsd.org

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to 
"freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CFT: if_bridge performance improvements

2020-04-24 Thread Xin Li
On 4/24/20 06:42, Kristof Provost wrote:
> On 22 Apr 2020, at 18:15, Xin Li wrote:
>> On 4/22/20 01:45, Kristof Provost wrote:
>>> On 22 Apr 2020, at 10:20, Xin Li wrote:
 Hi,

 On 4/14/20 02:51, Kristof Provost wrote:
> Hi,
>
> Thanks to support from The FreeBSD Foundation I’ve been able to
> work on
> improving the throughput of if_bridge.
> It changes the (data path) locking to use the NET_EPOCH
> infrastructure.
> Benchmarking shows substantial improvements (x5 in test setups).
>
> This work is ready for wider testing now.
>
> It’s under review here: https://reviews.freebsd.org/D24250
>
> Patch for CURRENT: https://reviews.freebsd.org/D24250?download=true
> Patches for stable/12:
> https://people.freebsd.org/~kp/if_bridge/stable_12/
>
> I’m not currently aware of any panics or issues resulting from these
> patches.

 I have observed the following panic with latest stable/12 after
 applying
 the stable_12 patchset, it appears like a race condition related NULL
 pointer deference, but I haven't took a deeper look yet.

 The box have 7 igb(4) NICs, with several bridge and VLAN configured
 acting as a router.  Please let me know if you need additional
 information; I can try -CURRENT as well, but it would take some time as
 the box is relatively slow (it's a ZFS based system so I can create a
 separate boot environment for -CURRENT if needed, but that would take
 some time as I might have to upgrade the packages, should there be any
 ABI breakages).

>>> Thanks for the report. I don’t immediately see how this could happen.
>>>
>>> Are you running an L2 firewall on that bridge by any chance? An earlier
>>> version of the patch had issues with a stray unlock in that code path.
>>
>> I don't think I have a L2 firewall (I assume means filtering based on
>> MAC address like what can be done with e.g. ipfw?  The bridges were
>> created on vlan interfaces though, do they count as L2 firewall?), the
>> system is using pf with a few NAT rules:
>>
> 
> That backtrace looks identical to the one Peter reported, up to and
> including the offset in the bridge_input() function.
> Given that there’s no likely way to end up with a NULL mutex either I
> have to assume that it’s a case of trying to unlock a locked mutex, and
> the most likely reason is that you ran into the same problem Peter ran
> into.
> 
> The current version of the patch should resolve it.

Thanks, I'd like to report that after applying the patch from Peter the
system seems to survive without problem.

Cheers,




signature.asc
Description: OpenPGP digital signature


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Michael Tuexen
> On 24. Apr 2020, at 21:06, Rodney W. Grimes  
> wrote:
> 
>> On Fri, Apr 24, 2020 at 01:31:35PM +0200, Kurt Jaeger wrote:
>>> 
>>> Thanks. Is BBR active automatically or is there a sysctl or
>>> socket option to activate it ?
>> 
>> net.inet.tcp.cc.available: List available congestion control algorithms
>> net.inet.tcp.cc.algorithm: Default congestion control algorithm
> 
> Start at:
> man mod_cc
BBR is conceptually a CC, but in FreeBSD it is NOT implemented as a CC module.
It is a TCP stack. You need to load it using
kldload tcp_bbr
and then either make it the default by
sudo sysctl net.inet.tcp.functions_default=bbr
or use the IPPROTO_TCP level socket option TCP_FUNCTION_BLK to set the stack
to BBR. The uperf test tool allows to set the TCP stack for measurements.
Please note that you need to compile the kernel with
makeoptions WITH_EXTRA_TCP_STACKS=1
options TCPHPTS

Best regards
Michael
> 
> 
> -- 
> Rod Grimes rgri...@freebsd.org
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Ordering of files in zoneinfo

2020-04-24 Thread Ed Maste
On Fri, 24 Apr 2020 at 07:23, Fabian Keil  wrote:
>
> > I wonder if we could drop the sort and replace ${TZS} in line 100 with
> > ${TZS:O} instead?
>
> Makes sense to me.

Agreed, that seems sensible.

> > By the way, looking at
> > https://github.com/freebsd/pkg/blob/master/libpkg/metalog.c , I wonder if
> > the sort should really happen in pkg(8) instead?
>
> Currently the METALOG is also used when creating the tarballs so sorting
> only in pkg would be insufficient as long as tarballs are still supported.

I think there are other reasons we'd like to keep METALOG itself in
deterministic order too, even if pkg can take care of it -- for
example, issues like PR234886 can be triggered by ordering (even
though the root cause is elsewhere and TZ ordering isn't going to lead
to exactly that kind of issue).
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Rodney W. Grimes
> On Fri, Apr 24, 2020 at 01:31:35PM +0200, Kurt Jaeger wrote:
> > 
> > Thanks. Is BBR active automatically or is there a sysctl or
> > socket option to activate it ?
> 
> net.inet.tcp.cc.available: List available congestion control algorithms
> net.inet.tcp.cc.algorithm: Default congestion control algorithm

Start at:
man mod_cc


-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Michael Tuexen
> On 24. Apr 2020, at 16:23, Mark Johnston  wrote:
> 
> On Fri, Apr 24, 2020 at 03:15:08PM +0100, Tom Jones wrote:
>> r...@freebsd.org
>> Bcc: 
>> Subject: Re: How to enable tcp bbr in FreeBSD???
>> Reply-To: 
>> In-Reply-To: <6042155a-297b-d85e-1d64-24d93da32...@gmail.com>
>> 
>> 
>> ... snip ...
>>> 
>>> Maybe it is not ready for prime time, i do not know why it is not in the
>>> default build.
>>> Maybe ask the committer.
>>> 
>> 
>> I have added rrs@ in cc and the freebsd-transport list. 
>> 
>> Does anyone know if there are plans to enable alternate TCP stacks in
>> generic? 
>> 
>> Is there a stability point we need to hit first?
> 
> There are a couple of open bugs found by syzkaller (complete with
> reproducers) that appeared when I enabled the alternate TCP stacks:
> 
> https://syzkaller.appspot.com/bug?id=986b4cecd84439df9794bda1a45d9cf0f50356fe
> https://syzkaller.appspot.com/bug?id=048f650e99696f881872a285cef0e3b9bd4f4e25
> 
> I'd expect these to be fixed before providing the alternate stacks in
> GENERIC.
We talked about these yesterday in the FreeBSD telco. At least some of them are
related to OOB data. The plan is to disable handling of OOB data in the 
alternate
stacks. Will bring up a patch and see if that fixes the issues.

Best regards
Michael
> ___
> freebsd-transp...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-transport
> To unsubscribe, send any mail to "freebsd-transport-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Mark Johnston
On Fri, Apr 24, 2020 at 03:15:08PM +0100, Tom Jones wrote:
> r...@freebsd.org
> Bcc: 
> Subject: Re: How to enable tcp bbr in FreeBSD???
> Reply-To: 
> In-Reply-To: <6042155a-297b-d85e-1d64-24d93da32...@gmail.com>
> 
> 
> ... snip ...
> > 
> > Maybe it is not ready for prime time, i do not know why it is not in the
> > default build.
> > Maybe ask the committer.
> > 
> 
> I have added rrs@ in cc and the freebsd-transport list. 
> 
> Does anyone know if there are plans to enable alternate TCP stacks in
> generic? 
> 
> Is there a stability point we need to hit first?

There are a couple of open bugs found by syzkaller (complete with
reproducers) that appeared when I enabled the alternate TCP stacks:

https://syzkaller.appspot.com/bug?id=986b4cecd84439df9794bda1a45d9cf0f50356fe
https://syzkaller.appspot.com/bug?id=048f650e99696f881872a285cef0e3b9bd4f4e25

I'd expect these to be fixed before providing the alternate stacks in
GENERIC.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


[no subject]

2020-04-24 Thread Tom Jones
r...@freebsd.org
Bcc: 
Subject: Re: How to enable tcp bbr in FreeBSD???
Reply-To: 
In-Reply-To: <6042155a-297b-d85e-1d64-24d93da32...@gmail.com>


... snip ...
> 
> Maybe it is not ready for prime time, i do not know why it is not in the
> default build.
> Maybe ask the committer.
> 

I have added rrs@ in cc and the freebsd-transport list. 

Does anyone know if there are plans to enable alternate TCP stacks in
generic? 

Is there a stability point we need to hit first?

- Tom
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Johan Hendriks


Op 24-04-2020 om 15:51 schreef ykla:
WITH_EXTRA_TCP_STACKS=1  in make.conf  ? And why not make it in kernel 
default?


在 2020年4月24日星期五,Johan Hendriks > 写道:



Op 24-04-2020 om 15:37 schreef Kurt Jaeger:

Hi!

You can enable the stack globally on new connections without
restarting the box or daemons by running these commands:

kldload tcp_bbr

sysctl net.inet.tcp.functions_inherit_listen_socket_stack=0
sysctl net.inet.tcp.functions_default=bbr

This fails on the box running 13.0:

# kldload tcp_bbr
kldload: can't load tcp_bbr: No such file or directory

So it looks it has to be hooked to the build somehow ?

And: man -k bbr has no results as well...

The commit message says the following:


This commit adds BBR (Bottleneck Bandwidth and RTT) congestion
control. This
is a completely separate TCP stack (tcp_bbr.ko) that will be built
only if
you add the make options WITH_EXTRA_TCP_STACKS=1 and also include
the option
TCPHPTS. You can also include the RATELIMIT option if you have a
NIC interface that
supports hardware pacing, BBR understands how to use such a feature.


So i think you need te rebuild with the following option set
WITH_EXTRA_TCP_STACKS=1

regards
Johan Hendriks

___
freebsd-current@freebsd.org 
mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current

To unsubscribe, send any mail to
"freebsd-current-unsubscr...@freebsd.org
"



It looks like you need to add the following to the kernel as well.

option TCPHPTS

Maybe it is not ready for prime time, i do not know why it is not in the 
default build.

Maybe ask the committer.

regards,
Johan


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread ykla
WITH_EXTRA_TCP_STACKS=1  in make.conf  ? And why not make it in kernel
default?

在 2020年4月24日星期五,Johan Hendriks  写道:

>
> Op 24-04-2020 om 15:37 schreef Kurt Jaeger:
>
>> Hi!
>>
>> You can enable the stack globally on new connections without
>>> restarting the box or daemons by running these commands:
>>>
>>> kldload tcp_bbr
>>>
>>> sysctl net.inet.tcp.functions_inherit_listen_socket_stack=0
>>> sysctl net.inet.tcp.functions_default=bbr
>>>
>> This fails on the box running 13.0:
>>
>> # kldload tcp_bbr
>> kldload: can't load tcp_bbr: No such file or directory
>>
>> So it looks it has to be hooked to the build somehow ?
>>
>> And: man -k bbr has no results as well...
>>
>> The commit message says the following:
>
>
> This commit adds BBR (Bottleneck Bandwidth and RTT) congestion control.
> This
> is a completely separate TCP stack (tcp_bbr.ko) that will be built only if
> you add the make options WITH_EXTRA_TCP_STACKS=1 and also include the
> option
> TCPHPTS. You can also include the RATELIMIT option if you have a NIC
> interface that
> supports hardware pacing, BBR understands how to use such a feature.
>
>
> So i think you need te rebuild with the following option set
> WITH_EXTRA_TCP_STACKS=1
>
> regards
> Johan Hendriks
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Johan Hendriks



Op 24-04-2020 om 15:37 schreef Kurt Jaeger:

Hi!


You can enable the stack globally on new connections without
restarting the box or daemons by running these commands:

kldload tcp_bbr

sysctl net.inet.tcp.functions_inherit_listen_socket_stack=0
sysctl net.inet.tcp.functions_default=bbr

This fails on the box running 13.0:

# kldload tcp_bbr
kldload: can't load tcp_bbr: No such file or directory

So it looks it has to be hooked to the build somehow ?

And: man -k bbr has no results as well...


The commit message says the following:


This commit adds BBR (Bottleneck Bandwidth and RTT) congestion control. This
is a completely separate TCP stack (tcp_bbr.ko) that will be built only if
you add the make options WITH_EXTRA_TCP_STACKS=1 and also include the option
TCPHPTS. You can also include the RATELIMIT option if you have a NIC 
interface that

supports hardware pacing, BBR understands how to use such a feature.


So i think you need te rebuild with the following option set 
WITH_EXTRA_TCP_STACKS=1


regards
Johan Hendriks

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CFT: if_bridge performance improvements

2020-04-24 Thread Kristof Provost

On 22 Apr 2020, at 18:15, Xin Li wrote:

On 4/22/20 01:45, Kristof Provost wrote:

On 22 Apr 2020, at 10:20, Xin Li wrote:

Hi,

On 4/14/20 02:51, Kristof Provost wrote:

Hi,

Thanks to support from The FreeBSD Foundation I’ve been able to 
work on

improving the throughput of if_bridge.
It changes the (data path) locking to use the NET_EPOCH 
infrastructure.

Benchmarking shows substantial improvements (x5 in test setups).

This work is ready for wider testing now.

It’s under review here: https://reviews.freebsd.org/D24250

Patch for CURRENT: https://reviews.freebsd.org/D24250?download=true
Patches for stable/12:
https://people.freebsd.org/~kp/if_bridge/stable_12/

I’m not currently aware of any panics or issues resulting from 
these

patches.


I have observed the following panic with latest stable/12 after 
applying
the stable_12 patchset, it appears like a race condition related 
NULL

pointer deference, but I haven't took a deeper look yet.

The box have 7 igb(4) NICs, with several bridge and VLAN configured
acting as a router.  Please let me know if you need additional
information; I can try -CURRENT as well, but it would take some time 
as
the box is relatively slow (it's a ZFS based system so I can create 
a
separate boot environment for -CURRENT if needed, but that would 
take
some time as I might have to upgrade the packages, should there be 
any

ABI breakages).

Thanks for the report. I don’t immediately see how this could 
happen.


Are you running an L2 firewall on that bridge by any chance? An 
earlier
version of the patch had issues with a stray unlock in that code 
path.


I don't think I have a L2 firewall (I assume means filtering based on
MAC address like what can be done with e.g. ipfw?  The bridges were
created on vlan interfaces though, do they count as L2 firewall?), the
system is using pf with a few NAT rules:



That backtrace looks identical to the one Peter reported, up to and 
including the offset in the bridge_input() function.
Given that there’s no likely way to end up with a NULL mutex either I 
have to assume that it’s a case of trying to unlock a locked mutex, 
and the most likely reason is that you ran into the same problem Peter 
ran into.


The current version of the patch should resolve it.

Best regards,
Kristof
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Kurt Jaeger
Hi!

> You can enable the stack globally on new connections without
> restarting the box or daemons by running these commands:
> 
> kldload tcp_bbr
> 
> sysctl net.inet.tcp.functions_inherit_listen_socket_stack=0
> sysctl net.inet.tcp.functions_default=bbr

This fails on the box running 13.0:

# kldload tcp_bbr 
kldload: can't load tcp_bbr: No such file or directory

So it looks it has to be hooked to the build somehow ?

And: man -k bbr has no results as well...

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread sthaug
> On my FreeBSD 13.0-CURRENT amd64 r359631M system:
> 
> $ sysctl -a | grep net.inet.tcp.cc
> [...]
> net.inet.tcp.cc.available: newreno
> net.inet.tcp.cc.algorithm: newreno
> 
> So it's more recent than the patch, but it does not offer anything
> besides newreno ?

Quoting an email here:

You can enable the stack globally on new connections without
restarting the box or daemons by running these commands:

kldload tcp_bbr

sysctl net.inet.tcp.functions_inherit_listen_socket_stack=0
sysctl net.inet.tcp.functions_default=bbr

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Kurt Jaeger
Hi!

> > Thanks. Is BBR active automatically or is there a sysctl or
> > socket option to activate it ?
> 
> net.inet.tcp.cc.available: List available congestion control algorithms
> net.inet.tcp.cc.algorithm: Default congestion control algorithm

Hmm, 

On my FreeBSD 13.0-CURRENT amd64 r359631M system:

$ sysctl -a | grep net.inet.tcp.cc
[...]
net.inet.tcp.cc.available: newreno
net.inet.tcp.cc.algorithm: newreno

So it's more recent than the patch, but it does not offer anything
besides newreno ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Herbert J. Skuhra
On Fri, Apr 24, 2020 at 01:31:35PM +0200, Kurt Jaeger wrote:
> 
> Thanks. Is BBR active automatically or is there a sysctl or
> socket option to activate it ?

net.inet.tcp.cc.available: List available congestion control algorithms
net.inet.tcp.cc.algorithm: Default congestion control algorithm

-- 
Herbert
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread rb
Hi,

> On 24 Apr 2020, at 12:31, Kurt Jaeger  wrote:
> 
> Hi!
> 
>>> On 24 Apr 2020, at 07:29, ykla  wrote:
>>> 
>>> I search by Google  but found no results about how to enable bbr in
>>> FreeBSD. BBR had developed in 2019. So I want to enable it.
>> 
>> See: https://svnweb.freebsd.org/base?view=revision=352657
> 
> Thanks. Is BBR active automatically or is there a sysctl or
> socket option to activate it ?

Sorry I only know what’s in the commit message.

> -- 
> p...@opsec.eu+49 171 3101372Now what ?
> 


--
Bob Bishop   t: +44 (0)118 940 1243
r...@gid.co.uk m: +44 (0)783 626 4518





___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD???

2020-04-24 Thread Kurt Jaeger
Hi!

> > On 24 Apr 2020, at 07:29, ykla  wrote:
> > 
> > I search by Google  but found no results about how to enable bbr in
> > FreeBSD. BBR had developed in 2019. So I want to enable it.
> 
> See: https://svnweb.freebsd.org/base?view=revision=352657

Thanks. Is BBR active automatically or is there a sysctl or
socket option to activate it ?

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: Ordering of files in zoneinfo

2020-04-24 Thread Fabian Keil
Xin LI  wrote:

> I have took a look at the change history, it seems that the find
> operation was introduced in r245265
>  (brooks@,
> to support packaged base) and sort was initially implemented as find -s
> in r289451
>  (ngie@,
> to make METALOG reproducible) then as sort in r328958
>  (imp@,
> for portability).
> 
> I wonder if we could drop the sort and replace ${TZS} in line 100 with
> ${TZS:O} instead?

Makes sense to me.
 
> By the way, looking at
> https://github.com/freebsd/pkg/blob/master/libpkg/metalog.c , I wonder if
> the sort should really happen in pkg(8) instead?

Currently the METALOG is also used when creating the tarballs so sorting
only in pkg would be insufficient as long as tarballs are still supported.

Fabian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: How to enable tcp bbr in FreeBSD?

2020-04-24 Thread Bob Bishop
Hi,

> On 24 Apr 2020, at 07:29, ykla  wrote:
> 
> I search by Google  but found no results about how to enable bbr in
> FreeBSD. BBR had developed in 2019. So I want to enable it.

See: https://svnweb.freebsd.org/base?view=revision=352657

--
Bob Bishop
r...@gid.co.uk




___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


How to enable tcp bbr in FreeBSD?

2020-04-24 Thread ykla
I search by Google  but found no results about how to enable bbr in
FreeBSD. BBR had developed in 2019. So I want to enable it.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"