Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

Le 15/04/2017 à 06:26, David Ahern a écrit : > +Nicolas > > On 4/14/17 7:51 PM, Vlad Yasevich wrote: >> On 04/10/2017 11:49 AM, David Ahern wrote: >>> On 4/10/17 9:39 AM, Vlad Yasevich wrote: OK, so this will work for the events that are generated as a result of device state change

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

+Nicolas On 4/14/17 7:51 PM, Vlad Yasevich wrote: > On 04/10/2017 11:49 AM, David Ahern wrote: >> On 4/10/17 9:39 AM, Vlad Yasevich wrote: >>> OK, so this will work for the events that are generated as a result of >>> device state change >>> (like mtu, address, and others). >>> >>> However, the

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 04/10/2017 11:49 AM, David Ahern wrote: > On 4/10/17 9:39 AM, Vlad Yasevich wrote: >> OK, so this will work for the events that are generated as a result of >> device state change >> (like mtu, address, and others). >> >> However, the original event data may be needed for other events that may

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 4/10/17 9:39 AM, Vlad Yasevich wrote: > OK, so this will work for the events that are generated as a result of device > state change > (like mtu, address, and others). > > However, the original event data may be needed for other events that may be > of use to userspace like

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 04/08/2017 02:18 PM, Roopa Prabhu wrote: > On 4/8/17, 11:13 AM, David Ahern wrote: >> On 4/8/17 2:06 PM, Roopa Prabhu wrote: >>> On 4/7/17, 2:25 PM, David Ahern wrote: Changing MTU on a link currently causes 3 messages to be sent to userspace: [LINK]11: dummy1:

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 4/8/17 9:36 PM, Vlad Yasevich wrote: > On 04/07/2017 05:25 PM, David Ahern wrote: >> Changing MTU on a link currently causes 3 messages to be sent to userspace: >> >> [LINK]11: dummy1: mtu 1490 qdisc noqueue state >> UNKNOWN group default event PRE_CHANGE_MTU >>

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 04/07/2017 05:25 PM, David Ahern wrote: > Changing MTU on a link currently causes 3 messages to be sent to userspace: > > [LINK]11: dummy1: mtu 1490 qdisc noqueue state > UNKNOWN group default event PRE_CHANGE_MTU > link/ether f2:52:5c:6d:21:f3 brd

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 4/8/17, 11:13 AM, David Ahern wrote: > On 4/8/17 2:06 PM, Roopa Prabhu wrote: >> On 4/7/17, 2:25 PM, David Ahern wrote: >>> Changing MTU on a link currently causes 3 messages to be sent to userspace: >>> >>> [LINK]11: dummy1: mtu 1490 qdisc noqueue >>> state

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 4/8/17 2:06 PM, Roopa Prabhu wrote: > On 4/7/17, 2:25 PM, David Ahern wrote: >> Changing MTU on a link currently causes 3 messages to be sent to userspace: >> >> [LINK]11: dummy1: mtu 1490 qdisc noqueue state >> UNKNOWN group default event PRE_CHANGE_MTU >>

Re: [PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

On 4/7/17, 2:25 PM, David Ahern wrote: > Changing MTU on a link currently causes 3 messages to be sent to userspace: > > [LINK]11: dummy1: mtu 1490 qdisc noqueue state > UNKNOWN group default event PRE_CHANGE_MTU > link/ether f2:52:5c:6d:21:f3 brd

[PATCH net-next 1/8] rtnetlink: Do not generate notifications for MTU events

Changing MTU on a link currently causes 3 messages to be sent to userspace: [LINK]11: dummy1: mtu 1490 qdisc noqueue state UNKNOWN group default event PRE_CHANGE_MTU link/ether f2:52:5c:6d:21:f3 brd ff:ff:ff:ff:ff:ff [LINK]11: dummy1: