On 02/14/13 05:37, Adrian Chadd wrote:
> On 13 February 2013 02:27, Andre Oppermann wrote:
>
>> Again I'd like to point out that this sort of modification should
>> be implemented as a congestion control module. All the hook points
>> are already there and can readily be used instead of adding m
On 02/14/13 01:48, Andre Oppermann wrote:
> On 13.02.2013 15:26, Lawrence Stewart wrote:
>> On 02/13/13 21:27, Andre Oppermann wrote:
>>> On 13.02.2013 09:25, Lawrence Stewart wrote:
The idea is useful. I'd just like to discuss the implementation
specifics a little further before recommen
Synopsis: [oce] [patch] Possible lock reversal and duplicate locks as reported
by Witness
Responsible-Changed-From-To: freebsd-net->jpaetzel
Responsible-Changed-By: jpaetzel
Responsible-Changed-When: Wed Feb 13 21:25:24 UTC 2013
Responsible-Changed-Why:
I'll take this one.
http://www.freebsd.or
.. and I should say, "competing / parallel" congestion algorithms. Ie
- how multiple CC's work for/against each other on the same "internet"
at the same time.
Adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/free
On 13 February 2013 02:27, Andre Oppermann wrote:
> Again I'd like to point out that this sort of modification should
> be implemented as a congestion control module. All the hook points
> are already there and can readily be used instead of adding more special
> cases to the generic part of TCP
On Feb 12, 2013, at 3:44 PM, Josef Pojsl wrote:
> Hello list,
>
> on a FreeBSD 8.3-RELEASE-p3, I have come across a problem with lacp
> protocol on a lagg interface. I have aggregated two interfaces with the
> same speed but slightly different type of media (namely 10Gbase-SR and
> 10Gbase-LR).
Old Synopsis: lagg/lacp broken when aggregated interfaces have same speed but
different media type
New Synopsis: [lagg] [patch] lagg/lacp broken when aggregated interfaces have
same speed but different media type
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: lini
On 13.02.2013 15:26, Lawrence Stewart wrote:
On 02/13/13 21:27, Andre Oppermann wrote:
On 13.02.2013 09:25, Lawrence Stewart wrote:
The idea is useful. I'd just like to discuss the implementation
specifics a little further before recommending whether the patch should
go in as is to provide a st
On 02/13/13 21:27, Andre Oppermann wrote:
> On 13.02.2013 09:25, Lawrence Stewart wrote:
>> FYI I've read the whole thread as of this reply and plan to follow up to
>> a few of the other posts separately, but first for my initial thoughts...
>>
>> On 01/23/13 07:11, John Baldwin wrote:
>>> As I men
On 02/10/13 16:05, Kevin Oberman wrote:
> On Sat, Feb 9, 2013 at 6:41 AM, Alfred Perlstein wrote:
>> On 2/7/13 12:04 PM, George Neville-Neil wrote:
>>>
>>> On Feb 6, 2013, at 12:28 , Alfred Perlstein wrote:
>>>
On 2/6/13 4:46 AM, John Baldwin wrote:
>
> On Wednesday, February 06, 201
On 02/08/13 07:04, George Neville-Neil wrote:
>
> On Feb 6, 2013, at 12:28 , Alfred Perlstein wrote:
>
>> On 2/6/13 4:46 AM, John Baldwin wrote:
>>> On Wednesday, February 06, 2013 6:27:04 am Randall Stewart wrote:
John:
A burst at line rate will *often* cause drops. This is becau
On 13.02.2013 09:25, Lawrence Stewart wrote:
FYI I've read the whole thread as of this reply and plan to follow up to
a few of the other posts separately, but first for my initial thoughts...
On 01/23/13 07:11, John Baldwin wrote:
As I mentioned in an earlier thread, I recently had to debug an
FYI I've read the whole thread as of this reply and plan to follow up to
a few of the other posts separately, but first for my initial thoughts...
On 01/23/13 07:11, John Baldwin wrote:
> As I mentioned in an earlier thread, I recently had to debug an issue we were
> seeing across a link with a h
13 matches
Mail list logo
