linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: aia21@cam.ac.uk
Cc: akpm@osdl.org, torvalds@osdl.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/11] FUSE - core
Date: Fri, 14 Jan 2005 15:32:33 +0100	[thread overview]
Message-ID: <E1CpSV7-0002Ac-00@dorka.pomaz.szeredi.hu> (raw)
In-Reply-To: <Pine.LNX.4.60.0501141409500.18572@hermes-1.csi.cam.ac.uk> (message from Anton Altaparmakov on Fri, 14 Jan 2005 14:14:12 +0000 (GMT))

> I prefer the _NOFS regardless (and others will probably disagree) because 
> it also means that if a machine is seriously running out of memory the fs 
> will give up with -ENOMEM much more readily with _NOFS rather than 
> increasing the memory pressure even further.  As I said, others probably 
> disagree with me...

Then you are suggesting to add __GFP_NORETRY, to all my allocations.
That's may well be a valid argument, if we want to treat userspace
filesystems less critical, than other things.

Adding _NOFS in the case where no deadlock is possible makes things
worse not better, since you are limiting the allocation from
performing I/O.  It's clearly a losing situation.

Thanks,
Miklos

  reply	other threads:[~2005-01-14 14:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 16:25 [PATCH 2/11] FUSE - core Miklos Szeredi
2005-01-12 22:36 ` Andrew Morton
2005-01-13  5:31   ` Miklos Szeredi
2005-01-14 13:55 ` Anton Altaparmakov
2005-01-14 14:07   ` Miklos Szeredi
2005-01-14 14:14     ` Anton Altaparmakov
2005-01-14 14:32       ` Miklos Szeredi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-10 18:58 Miklos Szeredi
2005-01-10 21:40 ` Mike Waychison
2005-01-10 22:28   ` Miklos Szeredi
2005-02-14 22:43 ` Faraz Ahmed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1CpSV7-0002Ac-00@dorka.pomaz.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=aia21@cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).