From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] -mm swsusp: copy_page is harmfull
Date: Mon, 04 Oct 2004 21:20:29 +1000 [thread overview]
Message-ID: <1096888829.9539.75.camel@gaston> (raw)
In-Reply-To: <20041004093330.GA7614@elf.ucw.cz>
On Mon, 2004-10-04 at 19:33, Pavel Machek wrote:
> Hmm but does it matter? Is that operation really that slow on ppc?
> This whole copy takes maybe second on x86, other operations are way
> slower...
No, you are right, it probably doesn't matter.
Ben.
prev parent reply other threads:[~2004-10-04 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409292014.i8TKEhov023334@hera.kernel.org>
2004-10-03 23:50 ` [PATCH] -mm swsusp: copy_page is harmfull Benjamin Herrenschmidt
2004-10-04 8:12 ` Nigel Cunningham
2004-10-04 9:33 ` Pavel Machek
2004-10-04 11:20 ` Benjamin Herrenschmidt [this message]
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=1096888829.9539.75.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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