lkml.org 
[lkml]   [2005]   [Jul]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] String conversions for memory policy
    Christoph wrote:
    > this could be construet as a single string

    I said "single token." I meant as in a single word, not a string of
    multiple tokens having its own internal syntax. Heck - if by 'string'
    you just mean a sequence of bytes, then I could construe any data
    representation as a 'string'.

    I don't know if it is a good idea in this case, but each time we add
    another pseudo file system interface to the kernel, we should make
    an effort to keep the contents of each such pseudo file to a number,
    a list of comparable numbers, or a single word.

    I'm pretty sure this convention (single number or word per file,
    or at most a list of numbers) has been encouraged elsewhere, though
    I don't see where offhand.

    I do think it is a good idea to be reluctant to introduce new magic
    syntax, such as seen in "bind={3/normal 1/high 0/dma}" in kernel-user
    interfaces. Though, as I noted in my previous post a few minutes ago,
    I sure hope we don't need zones here anyway - just nodes.

    --
    I won't rest till it's the best ...
    Programmer, Linux Scalability
    Paul Jackson <pj@sgi.com> 1.925.600.0401
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-07-31 03:49    [W:0.035 / U:31.548 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site