On 2/13/24 12:52, Ilya Maximets wrote:
On 2/13/24 09:28, Adrian Moreno wrote:
On 2/12/24 18:49, Ilya Maximets wrote:
On 2/12/24 09:43, Adrian Moreno wrote:
On 2/9/24 17:15, Ilya Maximets wrote:
On 2/9/24 08:06, Adrian Moreno wrote:
In order to properly balance bond traffic,
On 2/13/24 09:28, Adrian Moreno wrote:
>
>
> On 2/12/24 18:49, Ilya Maximets wrote:
>> On 2/12/24 09:43, Adrian Moreno wrote:
>>>
>>>
>>> On 2/9/24 17:15, Ilya Maximets wrote:
On 2/9/24 08:06, Adrian Moreno wrote:
> In order to properly balance bond traffic, ofproto/bond periodically
On 2/12/24 18:49, Ilya Maximets wrote:
On 2/12/24 09:43, Adrian Moreno wrote:
On 2/9/24 17:15, Ilya Maximets wrote:
On 2/9/24 08:06, Adrian Moreno wrote:
In order to properly balance bond traffic, ofproto/bond periodically
reads usage statistics of the post-recirculation rules (which are
On 2/12/24 09:43, Adrian Moreno wrote:
>
>
> On 2/9/24 17:15, Ilya Maximets wrote:
>> On 2/9/24 08:06, Adrian Moreno wrote:
>>> In order to properly balance bond traffic, ofproto/bond periodically
>>> reads usage statistics of the post-recirculation rules (which are added
>>> to a hidden
On 2/9/24 17:15, Ilya Maximets wrote:
On 2/9/24 08:06, Adrian Moreno wrote:
In order to properly balance bond traffic, ofproto/bond periodically
reads usage statistics of the post-recirculation rules (which are added
to a hidden internal table).
To do that, each "struct bond_entry" (which
On 2/9/24 08:06, Adrian Moreno wrote:
> In order to properly balance bond traffic, ofproto/bond periodically
> reads usage statistics of the post-recirculation rules (which are added
> to a hidden internal table).
>
> To do that, each "struct bond_entry" (which represents a hash within a
> bond)
In order to properly balance bond traffic, ofproto/bond periodically
reads usage statistics of the post-recirculation rules (which are added
to a hidden internal table).
To do that, each "struct bond_entry" (which represents a hash within a
bond) stores the last seen statistics for its rule. When
