Nick Piggin <nickpiggin@xxxxxxxxxxxx> wrote: > Then make a PG_private2 bit and use that. To what end? Are you suggesting I should have: PG_private2 = PG_private | PG_fscache That's redundant information and doesn't help anything really. My suggestion (PG_private and PG_fscache separate and independent) is pretty efficient to actually render into machine instructions, especially if the two bits are placed in the lower part of the word. On x86, the test for both bits can be done with a single TEST instruction, and on most RISC archs, a MOVE and a single AND will usually suffice. David -- This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
