Searched refs:freelist (Results 1 – 4 of 4) sorted by relevance
73 Memory that is freed is put into a per-cluster freelist. Even if the data was75 current cluster's freelist (again, to reduce cache effects). The freelist is a92 we can add it to the freelist - but this is not ideal. So, stackshot uses94 a good chunk size. The amount of memory added to the freelist is reported by
405 struct mbuf *freelist = NULL, *tail = NULL; in mptcp_input() local538 if (freelist == NULL) { in mptcp_input()539 freelist = m; in mptcp_input()570 if (freelist == NULL) { in mptcp_input()571 freelist = m; in mptcp_input()631 if (freelist) { in mptcp_input()632 m_freem(freelist); in mptcp_input()
2045 mbuf_ref_t m, freelist = NULL; in sosend() local2214 if (freelist == NULL && in sosend()2226 freelist = in sosend()2237 if (freelist == NULL && in sosend()2249 freelist = in sosend()2267 freelist == NULL && in sosend()2273 freelist = in sosend()2282 } else if (freelist == NULL && in sosend()2293 freelist = in sosend()2308 if (freelist != NULL && atomic && in sosend()[all …]
93 …-free (PUAF)*. When the VM thinks a page became unused, it adds it to a freelist of physical pages…