lkml.org 
[lkml]   [2002]   [Feb]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Date
    SubjectRe: read_proc issue
    That's a good solution in the general case but doesn't work for
    some of the proc entries that already exist. cpuinfo, for example.
    There seem to be a number of niche /proc methods already. A cache-on-open
    method would be very useful for files like cpuinfo and a number of other
    files for PPC.

    It sure would make accessing /proc files less whacky for user-code.

    } Another approach is to do the calculation open and remember it in per
    } fd private data. You can recover that and free it on release. It could
    } even be a buffer holding the actual "content"
    -
    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-03-22 13:24    [W:0.022 / U:91.100 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site