[lkml]   [2007]   [Oct]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: per BDI dirty limit (was Re: -mm merge plans for 2.6.24)
    > Subject: bdi: debugfs interface
    > Expose the BDI stats (and readahead window) in /debug/bdi/
    > I'm still thinking it should go into /sys somewhere, however I just noticed
    > not all block devices that have a queue have a /queue directory. Noticeably
    > those that use make_request_fn() as opposed to request_fn(). And then of
    > course there are the non-block/non-queue BDIs.
    > A BDI is basically the object that represents the 'thing' you dirty pages
    > against. For block devices that is related to the block device (and is
    > typically embedded in the queue object), for NFS mounts its the remote server
    > object of the client. For FUSE, yet again something else.
    > I appreciate the sysfs people their opinion that /sys/bdi/ might not be the
    > best from their POV, however I'm not seeing where to hook the BDI object from
    > so that it all makes sense, a few of the things are currently not exposed in
    > sysfs at all, like the NFS and FUSE things.
    > So, for now, I've exposed the thing in debugfs. Please suggest a better
    > alternative.
    > Miklos, Trond: could you suggest a better fmt for the bdi_init_fmt() for your
    > respective filesystems?

    For fuse:

    err = bdi_init_fmt(&fc->bdi, "fuse-%llu", (unsigned long long) fc->id);

    This would match the connection ID in /sys/fs/fuse/connections/*

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-10-26 17:09    [W:0.019 / U:21.576 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site