From: James Courtier-Dutton <James@superbug.co.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@lists.linux-foundation.org
Subject: Re: parallel suspend/resume
Date: Sat, 08 Dec 2007 11:08:41 +0000 [thread overview]
Message-ID: <475A7B39.7030106@superbug.co.uk> (raw)
In-Reply-To: <20071208102143.GA7195@elf.ucw.cz>
Pavel Machek wrote:
> On Sat 2007-12-08 09:00:44, Oliver Neukum wrote:
>
>> Am Freitag, 7. Dezember 2007 19:01:12 schrieb David Brownell:
>>
>>> FWIW the appended patch removes that rude "order of registration"
>>> policy, so that the suspend/resume list matches the device tree.
>>> It's behaved OK on PCs and, in light duty, a few development boards;
>>> I've carried it around most of this year.
>>>
>> As it is a tree, why not store it as such?
>>
>
> IIRC because we do not want recursive tree walkers in the kernel --
> stack limits.
>
>
Surely it is possible to code a tree walker that is not a recursive
function?
I believe you can use a simple loop and the heap to store state that
would otherwise be stored on the stack in a recursive function.
next prev parent reply other threads:[~2007-12-08 11:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 19:46 parallel suspend/resume Marcelo Tosatti
2007-10-09 15:54 ` Alan Stern
2007-12-07 15:51 ` Pavel Machek
2007-12-07 16:22 ` Alan Stern
2007-12-07 18:01 ` David Brownell
2007-12-07 19:33 ` Alan Stern
2007-12-08 20:46 ` Rafael J. Wysocki
2007-12-10 5:10 ` David Brownell
2007-12-10 17:57 ` Alan Stern
2007-12-08 8:00 ` Oliver Neukum
2007-12-08 10:21 ` Pavel Machek
2007-12-08 11:08 ` James Courtier-Dutton [this message]
2007-12-08 12:26 ` Oliver Neukum
2007-12-08 11:24 ` Oliver Neukum
2007-12-08 15:43 ` Alan Stern
2007-12-08 20:43 ` Rafael J. Wysocki
2007-12-09 13:23 ` Oliver Neukum
2007-12-09 15:31 ` Alan Stern
2007-12-08 16:26 ` Alan Stern
2007-12-08 22:00 ` Alan Stern
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=475A7B39.7030106@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=linux-pm@lists.linux-foundation.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