lkml.org 
[lkml]   [2008]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC] bitmap relative operator for mempolicy extensions
    Hi Ray,

    > > > i prefer another name [!relative].
    > >
    > > Any suggestions?
    > >
    > > I'll give the name some thought myself.
    > > I like good names, and this is the right
    > > time to get this one right.
    >
    > 'Relative map' implies a constant offset. What you have there is just
    > a map as relmap could be sparse (which, btw, would have been nice to
    > have in the example).
    >
    > map_bitmap violates your naming convention, bitmap_map isn't all that
    > clear, bitmap_remap is taken, and while it is one-to-one and onto, I
    > think calling it bitmap_bijection would lose everyone except the
    > mathematicians. bitmap_onto? bitmap_map_onto? bitmap_map_bitmap_onto?

    Thanks for many idea.
    I like bitmap_onto and/or bitmap_map_onto. :)


    - kosaki



    \
     
     \ /
      Last update: 2008-02-15 01:27    [W:0.024 / U:0.116 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site