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
> I'm somewhat confused by the complexity. Currently we can already have a
> lot of dirty pages from FUSE (up to the per BDI dirty limit - so
> basically up to the total dirty limit).
>
> How is having them dirty from mmap'ed writes different?

Nope, fuse never had dirty pages. It does normal writes
synchronously, just updating the cache.

The dirty accounting and then the per-bdi throttling basically made it
possible _at_all_ to have a chance at a writepage implementation which
is not deadlocky (so thanks for those ;).

But there's still the throttle_vm_writeout() thing, and the other
places where the kernel is waiting for a write to complete, which just
cannot be done within a constrained time if an unprivileged userspace
process is involved.

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 20:41    [W:0.305 / U:0.068 seconds]
©2003-2014 Jasper Spaans. Advertise on this site