Page MenuHomeFreeBSD

Add eventhandler for PCP network interface changes
ClosedPublic

Authored by • hselasky on Apr 11 2018, 9:47 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 1, 10:45 AM
Unknown Object (File)
Sun, Sep 27, 4:33 PM
Unknown Object (File)
Sun, Sep 27, 4:16 PM
Unknown Object (File)
Sun, Sep 27, 4:12 PM
Unknown Object (File)
Sun, Sep 27, 4:11 PM
Unknown Object (File)
Sun, Sep 27, 3:56 PM
Unknown Object (File)
Sun, Sep 27, 5:24 AM
Unknown Object (File)
Thu, Sep 10, 8:48 AM
Subscribers

Details

Summary

Define an eventhandler to receive configuration changes related to the PCP value on a network interface. (WIP)

Further define a function prototype for this kind of events.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

• hselasky edited the summary of this revision. (Show Details)
• hselasky edited the summary of this revision. (Show Details)
• hselasky retitled this revision from Add event for PCP network interface changes to Add eventhandler for PCP network interface changes.Apr 11 2018, 9:53 AM
• hselasky edited the summary of this revision. (Show Details)

Maybe it would be enough to just introduce new IFNET_EVENT_PCP type for ifnet_event?

That's also a possibility.

Any more comments?

--HPS

Update patch according to suggestion from ae@

This revision is now accepted and ready to land.Apr 11 2018, 10:45 AM

It is wrong, IMO, to not issue the PCP event on the same change for if_vlan.

sys/net/if_ethersubr.c
1135 ↗(On Diff #41360)

The event should not be issued if the pcp is not set, i.e. it should be only called in the 'else' branch.

sys/net/if_ethersubr.c
1135 ↗(On Diff #41360)

In this case we will not be notified when we want to reset PCP

sys/net/if_ethersubr.c
1135 ↗(On Diff #41360)

Ah, I'm wrong.

This revision now requires review to proceed.Apr 11 2018, 11:58 AM

What are the pros and cons of these alternatives?

--HPS

What are the pros and cons of these alternatives?

What alternatives ?

vlan-specific events are still not generated.

Generate PCP event for both VLAN and LAN as suggested by @kib

Hi Guys, Can you have a fresh look at this patch again? I would like to complete this and possibly MFC to 11-stable.

This revision is now accepted and ready to land.Apr 25 2018, 12:25 PM
This revision was automatically updated to reflect the committed changes.