From: Bill Davidsen <davidsen@tmr.com>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: Oliver Neukum <oliver@neukum.org>, Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suspend2 merge preparation: Rationale behind the freezer changes.
Date: Sat, 22 May 2004 10:11:01 -0400 [thread overview]
Message-ID: <40AF5F75.7000206@tmr.com> (raw)
In-Reply-To: <40AE837E.4030708@linuxmail.org>
Nigel Cunningham wrote:
> Hi.
>
> Oliver Neukum wrote:
>
>> Am Freitag, 21. Mai 2004 14:28 schrieb Nigel Cunningham:
>>
>>> Yes, but what order? I played with that problem for ages. Perhaps I
>>> just didn't find the right combination.
>>
>> How about recording the order of creation and do it in opposite order?
>
>
> We could add a field to the process struct to record that. (Since PIDs
> can wrap, they can't be relied upon for this).
I would never suggest keeping a process creation date for something
trivial, but since you seem to be proposing one for something major, the
process creation date could be available in the readdir of the /proc
directory. Assuming you intend to keep date at all and not just some
counter, of course.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
prev parent reply other threads:[~2004-05-22 14:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 6:49 Suspend2 merge preparation: Rationale behind the freezer changes Nigel Cunningham
2004-05-21 9:33 ` Pavel Machek
2004-05-21 12:28 ` Nigel Cunningham
2004-05-21 13:34 ` Pavel Machek
2004-05-22 2:43 ` Nigel Cunningham
2004-05-21 13:42 ` Oliver Neukum
2004-05-21 17:08 ` Pavel Machek
2004-05-21 17:12 ` Oliver Neukum
2004-05-21 17:15 ` Pavel Machek
2004-05-21 17:20 ` Oliver Neukum
2004-05-21 23:35 ` Herbert Xu
2004-05-22 2:47 ` Nigel Cunningham
2004-05-21 22:32 ` Nigel Cunningham
2004-05-22 14:11 ` Bill Davidsen [this message]
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=40AF5F75.7000206@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=oliver@neukum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.