- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 1 2019
Jul 24 2019
Jul 23 2019
In D21005#455734, @jacob.e.keller_intel.com wrote:This is built on top of https://reviews.freebsd.org/D21004
It could probably be backported, but isn't as necessary as the previous patch which is why I kept them separate.
Jun 24 2019
Wrap line to keep it under 80 cols
Jun 19 2019
Jun 18 2019
May 29 2019
This is fine -- this was a result of our code stripping process, I think.
May 10 2019
May 8 2019
May 6 2019
Apr 18 2019
Apr 17 2019
Attempt to fix paths for stable/11.
Apr 16 2019
- Replace a space after #define with tab
Apr 11 2019
- ifconfig: Add option to report VF status info
- ixl: Add a license to ifvfstatus.c
- ixl: Updates to if_ixl.c
- Add spare data fields to struct ifvfstatus
Mar 28 2019
Mar 19 2019
Anyone else have any feedback? It makes sense to me that the attach process for pseudo devices should use the context lock like the attach process for regular devices.
Should this revision get closed? Nothing's happened on it for months.
Mar 14 2019
Mar 13 2019
Mar 7 2019
Mar 5 2019
Mar 2 2019
Does this match what the Linux PF driver does?
Feb 27 2019
Feb 21 2019
Feb 15 2019
Feb 14 2019
Feb 7 2019
@piotr.pietruszewski_intel.com Are we going to abandon this for now?
Jan 31 2019
In D19041#407181, @marius wrote:Well, I would just have went with "PCI" but if you prefer to state all variants :)
Would it be a good idea to group the iflib drivers together in the config files, so it's obvious there?
Jan 29 2019
In D18402#392608, @v.maffione_gmail.com wrote:You're right. I realized that just now.
I guess I could try to modify iflib_netmap_txsync and iflib_netmap_rxsync.
This patch could still be useful for FreeBSD 11, where ixgbe does not use iflib (as far as I see from the code).
Having an invalid value for the head writeback value is problematic...I'll check out the PR.
@jeffrey.e.pieper_intel.com you should re-test this, now that Piotr has updated the patch.
Ensure that iflib(4) and associated drivers pass correct RIDs to bus_release_resource(9) by obtaining the RIDs via rman_get_rid(9) on the corresponding resources instead of using the RIDs initially passed to bus_alloc_resource_any(9) as the latter function may change those RIDs. Solely bnxt(4) was using the correct RIDs by caching the ones returned by bus_alloc_resource_any(9).