public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Paul Mackerras <paulus@samba.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-pm@lists.linux-foundation.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: shrinking memory for suspend?
Date: Fri, 4 May 2007 14:11:43 +0200	[thread overview]
Message-ID: <200705041411.44247.rjw@sisk.pl> (raw)
In-Reply-To: <17979.4019.603174.454513@cargo.ozlabs.ibm.com>

On Friday, 4 May 2007 12:49, Paul Mackerras wrote:
> Rafael J. Wysocki writes:
> 
> > IMO, the freezing of user space and the freezing of kernel threads are two
> > different issues.  While the freezing of user space is pretty straightforward,
> > the freezing of kernel threads is difficult.
> 
> In general I agree, but now that we have FUSE, plus the framework for
> doing device drivers in userspace (I have forgotten its name), it gets
> even more complicated because some userspace processes are now doing
> the sorts of things that kernel threads do.
> 
> This is relevant for me because I use encfs regularly, and encfs is
> based on FUSE.  What happens if there is an encfs filesystem mounted,
> and we freeze all userspace processes and then do a sys_sync()?  Does
> the system wait forever for the encfs filesystem to write out its
> dirty data?

Well, that's a good question and I'm afraid the answer is 'yes'.

Still, I think we can try to solve this particular problem instead of trying to
get rid of the freezing entirely, because it that case we'll have many other
problems to fix.

Greetings,
Rafael

  reply	other threads:[~2007-05-04 12:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 14:24 shrinking memory for suspend? Johannes Berg
2007-04-30 15:09 ` Alan Stern
2007-04-30 15:10 ` Rafael J. Wysocki
2007-04-30 15:09   ` Johannes Berg
2007-04-30 19:57     ` Rafael J. Wysocki
2007-05-02 11:29 ` Pavel Machek
2007-05-02 14:02   ` Johannes Berg
2007-05-03 10:17     ` Rafael J. Wysocki
2007-05-03 10:34       ` Paul Mackerras
2007-05-03 10:45         ` Rafael J. Wysocki
2007-05-03 12:51           ` Paul Mackerras
2007-05-03 13:15             ` Rafael J. Wysocki
2007-05-03 16:34             ` Pavel Machek
2007-05-03 14:34           ` Alan Stern
2007-05-03 16:39             ` Rafael J. Wysocki
2007-05-03 23:32             ` Paul Mackerras
2007-05-04  9:02               ` Rafael J. Wysocki
2007-05-04 10:49                 ` Paul Mackerras
2007-05-04 12:11                   ` Rafael J. Wysocki [this message]
2007-05-04 15:05               ` Alan Stern
2007-05-03 11:33       ` Johannes Berg
2007-05-03 12:56         ` Rafael J. Wysocki
2007-05-04 10:48           ` Johannes Berg

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=200705041411.44247.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=johannes@sipsolutions.net \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=paulus@samba.org \
    --cc=pavel@ucw.cz \
    /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