Lines Matching refs:use

56   for the buffer cache, and most client should either use `Z_NOWAIT` or `Z_WAITOK`.
112 as attackers tend to use data/pointer overlaps to carry out their exploitations.
114 The typed allocators use compiler support to infer signatures
213       Note that this is absolutely OK to use this variant
242       Note that this is absolutely OK to use this variant
282 This section covers how typed allocators should be adopted to use
287 should probably use OSObject as a base class. C++ operators
296 Note that idiomatic IOKit is supposed to use `OSTypeAlloc(Class)`.
308 to continue to use C++'s new and delete keywords to allocate/deallocate instances.
320 Alternatively, if you cannot use the mixin approach, you can use the
332 their implementation, you can use `IODeclareTypedOperators` paired with
378 described above. You should never use the operators on scalar types. Instead, you
379 should use the appropriate typed allocator API based on the semantics of the memory
385 The blessed way of wrapping and passing a C++ type allocation for use in the
386 libkern collection is using `OSValueObject`. Please do not use `OSData` for this
389 `OSValueObject<T>` allows you to safely use an `OSData` like API surface