From: Zan Lynx <zlynx@acm.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
jirislaby@gmail.com, megaraidlinux@lsi.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH #repost] SCSI: megaraid, fix suspend/resume sections
Date: Fri, 02 May 2008 11:15:33 -0600 [thread overview]
Message-ID: <1209748533.239501.10.camel@localhost> (raw)
In-Reply-To: <20080501153048.2a8d356f.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
On Thu, 2008-05-01 at 15:30 -0700, Andrew Morton wrote:
[cut]
> > CONFIG_HOTPLUG is only settable to 'n' if you're CONFIG_EMBEDDED which
> > has a zero set intersection with the users of megaraid, so in practical
> > terms, there's no actual box it could kill.
>
> who suspends and resumes servers?
I read an article not long ago about a guy running an AMD renderfarm.
He was working on power management techniques, including suspending
systems that weren't in use. It made a huge difference in power costs,
apparently.
I believe suspend is also used in some virtual server farms where
physical systems are resumed and virtuals are migrated to satisfy higher
CPU demands.
I could also see using it combined with a load balancer or proxy to
bring up backup web or database servers.
Compared to using networked/USB power bars or management controllers to
bring systems up and down, suspend/resume provides a faster response.
--
Zan Lynx <zlynx@acm.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-05-02 17:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 15:56 [PATCH #repost] SCSI: megaraid, fix suspend/resume sections Jiri Slaby
2008-05-01 15:56 ` Jiri Slaby
2008-05-01 19:51 ` Yang, Bo
2008-05-01 19:51 ` Yang, Bo
2008-05-01 21:23 ` Andrew Morton
2008-05-01 21:23 ` Andrew Morton
2008-05-01 21:34 ` Jiri Slaby
2008-05-01 22:05 ` James Bottomley
2008-05-01 22:30 ` Andrew Morton
2008-05-02 14:56 ` James Bottomley
2008-05-02 15:01 ` Jiri Slaby
2008-05-02 15:03 ` James Bottomley
2008-05-02 17:15 ` Zan Lynx [this message]
2008-05-14 14:54 ` Pavel Machek
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=1209748533.239501.10.camel@localhost \
--to=zlynx@acm.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux@lsi.com \
/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.