mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Nigel Cunningham <ncunningham@linuxmail.org>,
	Hu Gang <hugang@soulinfo.com>
Subject: Re: [RFC][PATCH] swsusp: do not use higher order allocations on resume [update 2]
Date: Mon, 7 Feb 2005 15:45:27 +0100	[thread overview]
Message-ID: <200502071545.27613.rjw@sisk.pl> (raw)
In-Reply-To: <20050207142706.GD8040@elf.ucw.cz>

Hi,

On Monday, 7 of February 2005 15:27, Pavel Machek wrote:
> Hi!
> 
> > > The following patch is (yet) an(other) attempt to eliminate the need for using higher
> > > order memory allocations on resume.  It accomplishes this by replacing the array
> > > of page backup entries with a list, so it is only necessary to allocate individual
> > > memory pages.  This approach makes it possible to avoid relocating many memory
> > > pages on resume (as a result, much less memory is used) and to simplify
> > > the assembly code that restores the image.
> > 
> > I have updated the resume patch to apply to the 2.6.11-rc3-mm1 kernel that
> > contains the suspend part and the x86_64-Speed-up-suspend patch.  The patch
> > is only for x86-64 and i386.
> > 
> > [Note: without this patch the resume process fails on my box ("out of memory")
> > during every 7th - 8th suspend/resume cycle, on the average.]

Well, this doesn't depend on the previous patch, apparently. ;-)
 
> Pssst. At this point, solution would be to revert the first part,
> too. 2.6.11 is too near to do anything else.

Oh, I didn't mean changing anything now (eg because of the missing ppc
assembly part).  However, the patch is useful for me so I thought I'd post it
in case someone else (using the -mm kernels) needed it.

Greets,
Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-02-07 14:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 23:19 [RFC][PATCH] swsusp: do not use higher order memory allocations on resume Rafael J. Wysocki
2005-01-31 23:19 ` [RFC][PATCH] swsusp: do not use higher order memory allocations [update] Rafael J. Wysocki
2005-02-07 11:08 ` [RFC][PATCH] swsusp: do not use higher order allocations on resume [update 2] Rafael J. Wysocki
2005-02-07 14:27   ` Pavel Machek
2005-02-07 14:45     ` Rafael J. Wysocki [this message]
2005-02-07 16:23   ` Pavel Machek
2005-02-08 18:29     ` Rafael J. Wysocki
2005-02-08 19:10       ` Pavel Machek
2005-02-08 22:28         ` Rafael J. Wysocki
2005-02-08 22:42       ` Pavel Machek
2005-02-08 23:22         ` Rafael J. Wysocki
2005-02-13  5:54           ` hugang
2005-02-13  6:11             ` hugang

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=200502071545.27613.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=hugang@soulinfo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.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

all inboxes | Powered by JetHome®