Re: [RFC] fuse writable mmap design

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Miklos Szeredi
Date: Thursday, November 15, 2007 - 12:37 pm

> I'm somewhat confused by the complexity. Currently we can already have a

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-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[RFC] fuse writable mmap design, Miklos Szeredi, (Thu Nov 15, 9:10 am)
Re: [RFC] fuse writable mmap design, Peter Zijlstra, (Thu Nov 15, 12:22 pm)
Re: [RFC] fuse writable mmap design, Miklos Szeredi, (Thu Nov 15, 12:37 pm)
Re: [RFC] fuse writable mmap design, Peter Zijlstra, (Thu Nov 15, 12:42 pm)
Re: [RFC] fuse writable mmap design, Miklos Szeredi, (Thu Nov 15, 12:57 pm)
Re: [RFC] fuse writable mmap design, Peter Zijlstra, (Thu Nov 15, 1:01 pm)
Re: [RFC] fuse writable mmap design, Miklos Szeredi, (Thu Nov 15, 1:11 pm)