From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Sreenivas.Bagalkote@lsil.com, Sumant.Patro@lsil.com,
jeff@garzik.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: megaraid_sas suspend ok, resume oops
Date: Wed, 30 Aug 2006 12:30:14 +1000 [thread overview]
Message-ID: <1156905015.3243.1.camel@nigel.suspend2.net> (raw)
In-Reply-To: <b6a2187b0608291845l17532458hf0aaf22e247b5b37@mail.gmail.com>
Hi.
On Wed, 2006-08-30 at 09:45 +0800, Jeff Chua wrote:
> On 8/30/06, Nigel Cunningham <ncunningham@linuxmail.org> wrote:
> >
> > Neither swsusp (as far as I know) or suspend2 support CONFIG_HIGHMEM64G
> > at the moment, I'm afraid.
> >
> > It's not impossible, we just haven't seen it as a priority worth putting
> > time into. Do you really have more than 4GB of RAM and want to suspend
> > to disk?
>
> It'll be really "nice" to have. Currently all the production systems
> simply shutdown all databases and applications and put systems to a
> halt. But, I'm thinking of implementing suspend_to_disk instead of
> shutdown the database and applications, so when power resumes, the
> system can carry on where it was left off. Nice, very nice feature to
> have.
> It's "nice" because nobody has tried, and if this works, I don't see
> why not use it for all machines in a data center.
>
> The DELL 2950 has 16GB of RAM, and will be running oracle database.
Ok. I'll give it a go then, but I'll tell you now that it will probably
take a while as I have a lot on my plate. Feel free to poke me :)
Nigel
next prev parent reply other threads:[~2006-08-30 2:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 17:04 megaraid_sas suspend ok, resume oops Jeff Chua
2006-08-28 21:55 ` Pavel Machek
2006-08-29 8:15 ` Jens Axboe
2006-08-29 12:22 ` Jeff Chua
2006-08-29 20:39 ` Fedora vs. swsusp (was Re: megaraid_sas suspend ok, resume oops) Pavel Machek
2006-08-31 17:05 ` Rafael J. Wysocki
2006-08-29 23:45 ` megaraid_sas suspend ok, resume oops Nigel Cunningham
2006-08-30 1:45 ` Jeff Chua
2006-08-30 2:30 ` Nigel Cunningham [this message]
2006-08-30 8:41 ` Jeff Chua
2006-08-30 8:54 ` Rafael J. Wysocki
2006-09-02 13:30 ` Dave Jones
2006-09-02 19:47 ` Rafael J. Wysocki
2006-09-02 20:10 ` Dave Jones
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=1156905015.3243.1.camel@nigel.suspend2.net \
--to=ncunningham@linuxmail.org \
--cc=Sreenivas.Bagalkote@lsil.com \
--cc=Sumant.Patro@lsil.com \
--cc=axboe@kernel.dk \
--cc=jeff.chua.linux@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
/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