On Mon, Jun 19, 2000 at 05:01:46PM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> "Andrew Reilly" writes:
> : That sounds way too hard.  Why not restrict suspend activity to
> : user-level processes and bring the kernel/drivers back up through
> : a regular boot process?  At least that way the hardware and drivers
> : will know what they are all up to, even if some of it has changed
> : in the mean time.
> Takes too long...  That's shutdown, not S4.

Yes.  But what is the difference, really?  As far as the
hardware is concerned, it's being booted.  If that process can
be sped up by using the "S4" mechanisms, why can't they be
applied to a regular boot process too?  [I'm thinking about a
kernel equivelant of the "clean shutdown" flag on file systems.]

Fundamentally, is there no way to get the kernel and drivers to
go through a full boot phase in a small fraction of the time
that it takes to repopulate 64M of RAM from disk? (*)

I'm concerned about trying to take short-cuts with booting,
because I've seen both the Toshiba laptop that I'm using now,
and my mother's HP desktop system hang horribly hard when they
should have been coming out of suspend.  (Both W'98.)

I like the idea that my laptop will save power by shutting down
after a while, but I don't want to get into trouble if I forget
whether I was docked or not, or whether the floppy was plugged
in or not, when next I turn it on.

(*) Speaking of which: why are we considering doing process
dumps into a _different_ swap-ish partition, instead of just
ensuring that all processes are sleeping in the normal swap
partition?  If that was done, then they would just page
themselves back in as needed, on wake-up.

Sorry for blathering.  This is just really interesting stuff.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to