[lkml]   [2004]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] [Request for inclusion] Filesystem in Userspace

> > The GFP_IO and GFP_FS pages are the _real_ protectors. They don't dip into
> > the (very limited) set of pages, they say "we can still free 90% of
> > memory, we just have to ignore that dangerous 10%".
> I don't see how this makes more problems to userspace filesystems.
> When you clear GFP_IO or GFP_FS for an allocation you are limiting
> yourself from freeing some sort of memory. But that will not make it
> easier to actually _get_ that memory.
> With FUSE the allocation is NOT limited. Deadlock will not happen
> since page writeback is non-blocking, so while more FUSE backed pages
> can't be written, other filesystem's pages can be written back. The
> situation is better not worse.
> What am I missing?

I believe problem is when there are no other filesystem's
pages.... and at that point FUSE is worse than kernel filesystems
because you do not have reserved pools to use for freeing memory.

People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
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: 2005-03-22 14:08    [W:0.279 / U:2.032 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site