Searched full:oblivious (Results 1 – 9 of 9) sorted by relevance
46 is to make flock() and fcntl() locks oblivious to each other. Both can
59 * odds. Both should be able to operate on the bitmap oblivious of the
299 This allows the user to be oblivious about the underlying buffering mechanism
102 rather to let the netfs remain oblivious.
45 * bpf_object in parts of USDT attachment, they are oblivious of each other's46 * existence and libbpf is just oblivious, dealing with bpf_object-specific
335 * oblivious to the format of the directory. Hence we can either get a block
62 staying oblivious to what said type actually is.
1427 * Linux vfs should be oblivious to changes between v0 and v2. in bnx2x_vf_mbx_acquire()
61 * oblivious of the offset.