Lines Matching refs:will
44 Note, however, one will rarely have to use it, as the core provides
80 awareness to buffer allocation and, as we will see later, its
99 be allocated. Indeed, the allocator will use the network interface to
102 the allocated space will be of the requested size plus, eventually,
104 size will be shrunk so the possible headers space and new size will
114 will successfully allocate 800 + 20 + 8 bytes of buffer for the new
121 will successfully allocate 1500 bytes, and where 20 + 8 bytes (IPv4 +
122 UDP headers) will not be used for the payload.
130 will allocate 800 bytes and no extra header space.
137 will allocate 1514 bytes, the MTU + Ethernet header space.
140 :c:func:`net_pkt_alloc_buffer`, as it will take into account the
141 existing buffer. It will also account for the header space if
143 that case, the newly allocated buffer space will be appended to the
160 will need to reference once more all the chain of net_buf before
185 length parameters: if it cannot r/w the given length it will
197 and will not affect the buffer length. By default, a newly allocated
228 point, it will fail because there is nothing to read at the cursor
238 This will reset the cursor of the pkt to the beginning of the buffer
252 mode back and forth at any time. The net_pkt will be set to overwrite
260 Now the same operators can be used, but it will be limited to the
296 in a contiguous area of the buffer, it will be way more efficient to
299 directly will save memory.
307 tell if the data will be in a contiguous area, and
335 the requested data. On the RX path, these headers will be read but not
350 If the data are in a contiguous area, it will advance the cursor
351 relevantly. If not, it will write the data and the cursor will be