Searched full:oblivious (Results 1 – 16 of 16) sorted by relevance
22 interrupt handlers are oblivious to this distinction and therefore it is not
29 interrupt handlers are oblivious to this distinction and therefore it is not
42 is to make flock() and fcntl() locks oblivious to each other. Both can
46 is to make flock() and fcntl() locks oblivious to each other. Both can
45 * important to do because string oblivious code may read past in do_strncpy_from_user()
207 ``atomic_*``, etc.), but is oblivious of any ordering guarantees and simply
299 This allows the user to be oblivious about the underlying buffering mechanism
101 rather to let the netfs remain oblivious.
313 * oblivious to the format of the directory. Hence we can either get a block
273 * oblivious to the format of the directory. Hence we can either get a block
1641 /* XXX submission method oblivious? */ in intel_enable_engine_stats()
102 rather to let the netfs remain oblivious.
1425 * Linux vfs should be oblivious to changes between v0 and v2. in bnx2x_vf_mbx_acquire()
1428 * Linux vfs should be oblivious to changes between v0 and v2. in bnx2x_vf_mbx_acquire()
57 * oblivious of the offset.