Searched hist:"027 fda80fe8b8f7f76c9e1799753601674954901" (Results 1 – 3 of 3) sorted by relevance
| /freebsd/sys/netinet/ |
| H A D | toecore.h | diff 027fda80fe8b8f7f76c9e1799753601674954901 Mon Mar 18 16:49:39 CET 2024 Gleb Smirnoff <glebius@FreeBSD.org> inpcb: remove unused KPIs to manipulate inpcbs
These KPIs were added in 9d29c635daa69 and through 15 years had zero use.
They slightly remind what IfAPI does for struct ifnet. But IfAPI does
that for the sake of large collection of NIC drivers not being aware of
struct ifnet. For the inpcb it is unclear what could be a large
collection of externally written kernel modules that need extensively use
inpcb and not be aware of its internals at the same time. This isolation
of a structure knowledge requires a lot of work, and just throwing in a
few KPIs isn't helpful.
Reviewed by: kib, bz, markj
Differential Revision: https://reviews.freebsd.org/D44310
|
| H A D | in_pcb.h | diff 027fda80fe8b8f7f76c9e1799753601674954901 Mon Mar 18 16:49:39 CET 2024 Gleb Smirnoff <glebius@FreeBSD.org> inpcb: remove unused KPIs to manipulate inpcbs
These KPIs were added in 9d29c635daa69 and through 15 years had zero use.
They slightly remind what IfAPI does for struct ifnet. But IfAPI does
that for the sake of large collection of NIC drivers not being aware of
struct ifnet. For the inpcb it is unclear what could be a large
collection of externally written kernel modules that need extensively use
inpcb and not be aware of its internals at the same time. This isolation
of a structure knowledge requires a lot of work, and just throwing in a
few KPIs isn't helpful.
Reviewed by: kib, bz, markj
Differential Revision: https://reviews.freebsd.org/D44310
|
| H A D | in_pcb.c | diff 027fda80fe8b8f7f76c9e1799753601674954901 Mon Mar 18 16:49:39 CET 2024 Gleb Smirnoff <glebius@FreeBSD.org> inpcb: remove unused KPIs to manipulate inpcbs
These KPIs were added in 9d29c635daa69 and through 15 years had zero use.
They slightly remind what IfAPI does for struct ifnet. But IfAPI does
that for the sake of large collection of NIC drivers not being aware of
struct ifnet. For the inpcb it is unclear what could be a large
collection of externally written kernel modules that need extensively use
inpcb and not be aware of its internals at the same time. This isolation
of a structure knowledge requires a lot of work, and just throwing in a
few KPIs isn't helpful.
Reviewed by: kib, bz, markj
Differential Revision: https://reviews.freebsd.org/D44310
|