public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-kernel@vger.kernel.org
Cc: Stefan Seyfried <seife@suse.de>, Andrew Morton <akpm@osdl.org>,
	Pavel Machek <pavel@suse.cz>
Subject: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64
Date: Sun, 26 Sep 2004 19:06:10 +0200	[thread overview]
Message-ID: <200409261906.10635.rjw@sisk.pl> (raw)
In-Reply-To: <200409261345.10565.rjw@sisk.pl>

On Sunday 26 of September 2004 13:45, Rafael J. Wysocki wrote:
[-- snip --]
>  swsusp: Image: 11145 Pages
>  swsusp: Pagedir: 0 Pages
> Writing data to swap (11145 pages)...   0%
> 
> Here I have to press the red button unless I want to wait for a couple of 
> hours.  I'll send you more info when there's more.

I figured out that the slowdown occurs in device_resume(), so I put a printk() 
in dpm_resume(), like this:

--- drivers/base/power/resume.c 2004-09-26 16:44:09.000000000 +0200
+++ drivers/base/power/resume.c.rjw     2004-09-26 16:43:57.000000000 +0200
@@ -34,6 +34,7 @@
        while(!list_empty(&dpm_off)) {
                struct list_head * entry = dpm_off.next;
                struct device * dev = to_device(entry);
+               printk("%ld\n",  jiffies/HZ);
                list_del_init(entry);

                if (!dev->power.prev_state)

>From it, I have got the following results:

PM: writing image.
4294807
[ ... ]
4294807
PCI: Setting latency timer of device 0000:00:02.0 to 64
4294813
PCI: Setting latency timer of device 0000:00:02.1 to 64
4294817
PCI: Setting latency timer of device 0000:00:02.2 to 64
4294821
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
4294822
[ ... ]
4294822
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
4294822
4294825
4294828
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
4294828
[ ... ]
4294828
4294829
[ ... ]
4294829

As you can see, the difference between the first and the last timestamp is 22.  
However, if I make the same change in 2.6.9-rc2-mm1, I get:

PM: writing image.
4294761
[ ... ]
4294761
PCI: Setting latency timer of device 0000:00:02.0 to 64
4294761
PCI: Setting latency timer of device 0000:00:02.1 to 64
4294761
PCI: Setting latency timer of device 0000:00:02.2 to 64
4294761
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:06.0 to 64
4294762
[ ... ]
4294762
ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 11 (level, low) -> IRQ 11
4294762
4294762
4294762
ACPI: PCI interrupt 0000:02:01.2[C] -> GSI 11 (level, low) -> IRQ 11
4294762
[ ... ]
4294762

so the difference between the first and the last timestamp is 1 (ie 22 times 
less).

Now, I have no idea about what may be responsible for such a slowdown, but I 
suspect that it's related to PCI.  I really don't know what to look for, so 
if you can give me any hint, please do.

Greets,
RJW

-- 
- 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"

  parent reply	other threads:[~2004-09-26 17:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-25 10:14 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 Rafael J. Wysocki
2004-09-25 21:33 ` Stefan Seyfried
2004-09-26 10:02   ` Rafael J. Wysocki
2004-09-26 10:10     ` Pavel Machek
2004-09-26 11:45     ` Rafael J. Wysocki
2004-09-26 13:22       ` Pavel Machek
2004-09-26 17:06       ` Rafael J. Wysocki [this message]
2004-09-26 18:34         ` Pavel Machek
2004-09-26 19:25           ` Rafael J. Wysocki
2004-09-26 20:48             ` Stefan Seyfried
2004-09-26 22:05               ` Rafael J. Wysocki
2004-09-26 22:41               ` Pavel Machek
2004-09-25 23:40 ` Pavel Machek
2004-09-26 10:08   ` Rafael J. Wysocki
2004-09-26 10:09     ` Pavel Machek
2004-09-26 11:37       ` Rafael J. Wysocki
2004-09-26 13:20         ` Pavel Machek
2004-09-27 23:23           ` 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 (update) Rafael J. Wysocki
2004-09-28  2:03             ` Narayan Desai
2004-09-29 21:58             ` 2.6.9-rc2-mm[2-4]: zaphod-scheduler.patch makes swsusp incredibly slow (was: Re: 2.6.9-rc2-mm3: swsusp horribly slow on AMD64) Rafael J. Wysocki
2004-09-29 22:50               ` Pavel Machek
2004-09-26 21:00         ` 2.6.9-rc2-mm3: swsusp horribly slow on AMD64 Stefan Seyfried
2004-09-26 22:01           ` Rafael J. Wysocki
2004-09-26 22:33             ` Pavel Machek
2004-09-27  9:11               ` Rafael J. Wysocki

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=200409261906.10635.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=seife@suse.de \
    /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