Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK

Quoting r. Roland Dreier <[email protected]>:
> Michael, what led you to choose 0x30 and 0x31 for the two new values?
> It does seem that keeping them uniform across architectures is a
> reasonable thing to do, but as far as I can tell the values 9 and 10
> are unused on all architectures, and have the added merit of not
> falling in the parisc reserved range.

No particular reason - I just selected values away from the rest of pack.
Lets go ahead and change them.
 
> Do we still have a chance to change this?
So, any value consistent across architectures will do.

-- 
Michael S. Tsirkin
Staff Engineer, Mellanox Technologies
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
    • From: Linus Torvalds <[email protected]>
  • Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
    • From: Hugh Dickins <[email protected]>
  • Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
    • From: "Michael S. Tsirkin" <[email protected]>
  • Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
    • From: Hugh Dickins <[email protected]>
  • Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
    • From: Linus Torvalds <[email protected]>
  • Re: Re: madvise MADV_DONTFORK/MADV_DOFORK
    • From: "Michael S. Tsirkin" <[email protected]>
  • Re: Re: madvise MADV_DONTFORK/MADV_DOFORK
    • From: Hugh Dickins <[email protected]>
  • [PATCH] madvise MADV_DONTFORK/MADV_DOFORK
    • From: "Michael S. Tsirkin" <[email protected]>
  • Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK
    • From: Nick Piggin <[email protected]>
  • Re: [PATCH] madvise MADV_DONTFORK/MADV_DOFORK
    • From: Roland Dreier <[email protected]>

• Prev by Date: Re: [PATCH] Fix up MADV_DONTFORK/MADV_DOFORK definitions
• Next by Date: Re: [PATCH] Cpuset: oops in exit on null cpuset fix
• Previous by thread: Re: [PATCH] Fix up MADV_DONTFORK/MADV_DOFORK definitions
• Next by thread: Re: Re: madvise MADV_DONTFORK/MADV_DOFORK
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]