lkml.org 
[lkml]   [2007]   [Nov]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC] fuse writable mmap design
    From
    Date
    > > OTOH, I'm thinking about adding a per-fs limit (adjustable for
    > > privileged mounts) of dirty+writeback.
    > >
    > > I'm not sure how hard would it be to add support for this into
    > > balance_dirty_pages(). So I'm thinking of a parameter in struct
    > > backing_dev_info that is used to clip the calculated per-bdi threshold
    > > below this maximum.
    > >
    > > How would that affect the proportions algorithm? What would happen to
    > > the unused portion? Would it adapt to the slowed writeback and
    > > allocate it to some other writer?
    >
    > The unused part is gone, I've not yet found a way to re-distribute this
    > fairly.
    >
    > [ It's one of my open-problems, I can do a min_ratio per bdi, but not
    > yet a max_ratio ]

    OK, I'll bear this in mind.

    Limiting the number of dirty+writeback to << dirty_thresh could still
    make sense, since it could prevent a nasty filesystem from pinning
    lots of kernel memory (which it can do without fuse in other ways, so
    this is not very important IMO).

    Miklos
    -
    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: 2007-11-15 21:15    [W:2.504 / U:0.404 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site