From: Nigel Cunningham <ncunningham@crca.org.au>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: rjw@sisk.pl, linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] Freezer: Don't count threads waiting for frozen filesystems.
Date: Wed, 29 Oct 2008 09:03:25 +1100 [thread overview]
Message-ID: <1225231405.9661.18.camel@nigel-laptop> (raw)
In-Reply-To: <E1KuwTn-0006EQ-8J@pomaz-ex.szeredi.hu>
Hi.
On Tue, 2008-10-28 at 22:51 +0100, Miklos Szeredi wrote:
> On Wed, 29 Oct 2008, Nigel Cunningham wrote:
> > > However it does not fix the freezing of tasks which are waiting for
> > > VFS locks (i.e. inode->i_mutex) held by the outstanding fuse requests.
> > > This is the tricky part...
> >
> > Convert them all to wait_event_freezeable.
>
> You mean convert mutexes to event queues? Not a very good idea.
No, I don't. Sorry. I was thinking you were referring to the wait_event
calls in the fuse request code. My bad.
Perhaps it's best to go back to my original position: hold new requests
and allow existing ones to complete. I'll look again at previous
messages to see why you thought that was problematic.
Regards,
Nigel
next prev parent reply other threads:[~2008-10-28 22:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1224886068.6478.21.camel@nigel-laptop>
2008-10-26 20:01 ` [linux-pm] Freezer: Don't count threads waiting for frozen filesystems Rafael J. Wysocki
2008-10-27 11:12 ` Miklos Szeredi
2008-10-27 11:20 ` Nigel Cunningham
2008-10-27 11:37 ` Rafael J. Wysocki
2008-10-27 11:40 ` Nigel Cunningham
2008-10-27 12:38 ` Miklos Szeredi
2008-10-27 20:59 ` Nigel Cunningham
2008-10-27 21:09 ` Miklos Szeredi
2008-10-27 22:13 ` Nigel Cunningham
2008-10-28 20:25 ` Miklos Szeredi
2008-10-28 21:29 ` Nigel Cunningham
2008-10-28 21:51 ` Miklos Szeredi
2008-10-28 22:00 ` Rafael J. Wysocki
2008-10-28 22:02 ` Miklos Szeredi
2008-10-28 22:21 ` Rafael J. Wysocki
2008-10-28 23:21 ` Miklos Szeredi
2008-10-28 23:59 ` Rafael J. Wysocki
2008-10-29 8:10 ` Miklos Szeredi
2008-10-29 13:51 ` Alan Stern
2008-10-29 14:50 ` Miklos Szeredi
2008-10-29 15:28 ` Alan Stern
2008-10-29 15:50 ` Miklos Szeredi
2008-10-29 16:17 ` Alan Stern
2008-10-29 16:10 ` Miklos Szeredi
2008-10-29 20:37 ` Alan Stern
2008-10-29 21:11 ` Rafael J. Wysocki
2008-10-29 21:45 ` Nigel Cunningham
2008-10-29 22:07 ` Rafael J. Wysocki
2008-10-29 23:53 ` Miklos Szeredi
2008-11-09 13:44 ` Pavel Machek
2008-10-29 23:48 ` Miklos Szeredi
2008-10-30 13:04 ` Nigel Cunningham
2008-10-30 13:56 ` Alan Stern
2008-10-30 21:44 ` Nigel Cunningham
2008-10-31 8:49 ` Miklos Szeredi
2008-10-31 9:10 ` Nigel Cunningham
2008-10-31 9:16 ` Miklos Szeredi
2008-10-31 11:28 ` Nigel Cunningham
2008-10-31 12:44 ` Miklos Szeredi
2008-10-31 21:11 ` Nigel Cunningham
2008-10-29 23:43 ` Miklos Szeredi
2008-10-30 13:54 ` Alan Stern
2008-10-30 14:39 ` Miklos Szeredi
2008-10-30 17:07 ` Alan Stern
2008-10-30 17:43 ` Miklos Szeredi
2008-10-30 20:17 ` Rafael J. Wysocki
2008-11-15 16:58 ` Pavel Machek
2008-10-29 23:56 ` Matthew Garrett
2008-10-28 22:03 ` Nigel Cunningham [this message]
2008-10-28 23:04 ` Nigel Cunningham
2008-10-28 23:12 ` Miklos Szeredi
2008-10-28 23:17 ` Nigel Cunningham
2008-10-28 23:24 ` Miklos Szeredi
2008-10-28 23:41 ` Nigel Cunningham
2008-10-28 23:45 ` Miklos Szeredi
2008-10-28 23:50 ` Miklos Szeredi
2008-10-28 23:58 ` Nigel Cunningham
2008-10-28 23:54 ` Nigel Cunningham
2008-10-27 11:37 ` Miklos Szeredi
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=1225231405.9661.18.camel@nigel-laptop \
--to=ncunningham@crca.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
--cc=rjw@sisk.pl \
/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