Searched hist:172463 (Results 1 - 3 of 3) sorted by relevance
| /freebsd-11-stable/sys/kern/ | ||
| H A D | kern_mbuf.c | diff 172463 Sat Oct 06 19:42:39 MDT 2007 kmacy This patch adds an M_NOFREE flag which allows one to mark an mbuf as not being independently freeable. This allows one to embed an mbuf in the cluster itself. This confers the benefits of the packet zone on all cluster sizes. Embedded mbufs currently suffer from the same limitation that packet zone mbufs do in that one cannot disconnect them and pass them around independently of the cluster. It would likely be possible to eliminate this limitation in the future by adding a second reference for the mbuf itself. Approved by: re(gnn) |
| H A D | uipc_mbuf.c | diff 172463 Sat Oct 06 19:42:39 MDT 2007 kmacy This patch adds an M_NOFREE flag which allows one to mark an mbuf as not being independently freeable. This allows one to embed an mbuf in the cluster itself. This confers the benefits of the packet zone on all cluster sizes. Embedded mbufs currently suffer from the same limitation that packet zone mbufs do in that one cannot disconnect them and pass them around independently of the cluster. It would likely be possible to eliminate this limitation in the future by adding a second reference for the mbuf itself. Approved by: re(gnn) |
| /freebsd-11-stable/sys/sys/ | ||
| H A D | mbuf.h | diff 172463 Sat Oct 06 19:42:39 MDT 2007 kmacy This patch adds an M_NOFREE flag which allows one to mark an mbuf as not being independently freeable. This allows one to embed an mbuf in the cluster itself. This confers the benefits of the packet zone on all cluster sizes. Embedded mbufs currently suffer from the same limitation that packet zone mbufs do in that one cannot disconnect them and pass them around independently of the cluster. It would likely be possible to eliminate this limitation in the future by adding a second reference for the mbuf itself. Approved by: re(gnn) |
Completed in 245 milliseconds