- User Since
- Jan 27 2015, 7:34 PM (264 w, 2 d)
Wed, Feb 12
Is there a reason that these syctls would need "CTLFLAG_NEEDSGIANT", or does this patch default to that flag because it's a safe default if the contents of the sysctl are unknown? I'm aware of the previous review that added these flags, but I didn't get to look at it too closely.
Jan 13 2020
Jan 10 2020
Jan 3 2020
Can this get regenerated? It no longer applies cleanly.
Jan 2 2020
Dec 19 2019
Dec 3 2019
Dec 2 2019
Nov 21 2019
Nov 5 2019
Builds okay now.
Nov 4 2019
Don't remove the extra whitespace in if.c
Update patch to make it build on HEAD
I get a build error with this revision:
Adding @jpaetzel since he seemed to be the last person making updates to oce(4); is this change ok to make there? There's no functional change.
@jacob.e.keller_intel.com, is this ready to be committed?
Oct 30 2019
Oct 23 2019
Update review with a first cut version of the code that checks the bus
ranges of upstream pci bridges; this doesn't incorporate suggestions
that jhb@ had made.
Oct 21 2019
- Add a specific iflib flag for VLAN anti-spoof and use it
Oct 18 2019
Resolve merge conflict
Oct 16 2019
Oct 15 2019
Oct 10 2019
Oct 9 2019
Oct 8 2019
Here's the output I got from the first pcib above ice4/ice5 in devinfo:
I like the changes for the Intel ethernet drivers. I've always been uncomfortable with how we were required to manually iterate through the list in the driver using the LIST_FOREACH macros; like you say in your description, if the data structure changes, then it causes a lot of driver thrash.
@krzysztof.galazka_intel.com did this get tested yet?
Oct 4 2019
Sep 30 2019
Relevant bugzilla: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240610
Bugzilla link: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240610