Displaying 4 results from an estimated 4 matches for "__ethtool_init_settings".
2016 Jan 30
1
bonding (IEEE 802.3ad) not working with qemu/virtio
...evices
in ethtool that returns 10Gbps with the settings set like veth does
sounds good to me. What do you think ?
In fact they all set the same settings (apart from speed) so we can
consolidate them in a single default setting init function and for the
ones using different speed do something like:
__ethtool_init_settings(); <- sets everything like veth would with 10Mbps speed
__ethtool_cmd_speed_set(cmd, SPEED_10000);
And we're done.
2016 Jan 30
1
bonding (IEEE 802.3ad) not working with qemu/virtio
...evices
in ethtool that returns 10Gbps with the settings set like veth does
sounds good to me. What do you think ?
In fact they all set the same settings (apart from speed) so we can
consolidate them in a single default setting init function and for the
ones using different speed do something like:
__ethtool_init_settings(); <- sets everything like veth would with 10Mbps speed
__ethtool_cmd_speed_set(cmd, SPEED_10000);
And we're done.
2016 Jan 29
5
bonding (IEEE 802.3ad) not working with qemu/virtio
On 01/29/2016 10:45 PM, Jay Vosburgh wrote:
> Nikolay Aleksandrov <nikolay at cumulusnetworks.com> wrote:
>
>> On 01/25/2016 05:24 PM, Bj?rnar Ness wrote:
>>> As subject says, 802.3ad bonding is not working with virtio network model.
>>>
>>> The only errors I see is:
>>>
>>> No 802.3ad response from the link partner for any adapters
2016 Jan 29
5
bonding (IEEE 802.3ad) not working with qemu/virtio
On 01/29/2016 10:45 PM, Jay Vosburgh wrote:
> Nikolay Aleksandrov <nikolay at cumulusnetworks.com> wrote:
>
>> On 01/25/2016 05:24 PM, Bj?rnar Ness wrote:
>>> As subject says, 802.3ad bonding is not working with virtio network model.
>>>
>>> The only errors I see is:
>>>
>>> No 802.3ad response from the link partner for any adapters