mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mark Lord <lkml@rtr.ca>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] swsusp: separate swap-writing/reading code
Date: Fri, 24 Mar 2006 00:39:41 +0100	[thread overview]
Message-ID: <200603240039.42165.rjw@sisk.pl> (raw)
In-Reply-To: <442325DA.80300@rtr.ca>

Hi,

On Thursday 23 March 2006 23:48, Mark Lord wrote:
> Rafael J. Wysocki wrote:
> >
> > I agree it probably may be improved.  Still it seems to be good enough.  Further,
> > it's more efficient than the previous solution, so I consider it as an improvement.
> > Also this code has been tested for quite some time in -mm and appears to
> > behave properly, at least we haven't got any bug reports related to it so far.
> 
> I find the in-kernel swsusp to be quite slow, and it seems to use
> an awful lot of memory for book-keeping.  So count that as encouragement
> to improve the performance when you can.

This particular patch actually decreases the amount of memory used by swsusp.

Moreover I have _nothing_ against improvements, but it requires some time to
improve things.

> > Currently I'm not working on any better solution.  If you can provide any
> > patches to implement one, please submit them, but I think they'll have to be
> > tested for as long as this code, in -mm.
> 
> It would be *really nice* if you guys could stop being so underhandedly
> nasty in every single reply to anything from Nigel.

Well, you know, it's generally easy to say that something's done in a wrong
way, but this alone doesn't help _anyone_.

Suggestions are nice, but _someone_ has to implement them and I think
Nigel is more than capable of doing it in this particular case.  Also the code
in question is quite sensitive and such that it should be tested for a longer
time IMO.

That's what I was trying to say and it was not my intention to be nasty at all.

Greetings,
Rafael

  reply	other threads:[~2006-03-23 23:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200603231702.k2NH2OSC006774@hera.kernel.org>
2006-03-23 21:13 ` Nigel Cunningham
2006-03-23 21:53   ` Rafael J. Wysocki
2006-03-23 22:48     ` Mark Lord
2006-03-23 23:39       ` Rafael J. Wysocki [this message]
2006-03-27 10:26       ` Pavel Machek
2006-03-27 10:43         ` Nigel Cunningham
2006-03-27 23:15           ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-27 23:36             ` Nigel Cunningham
2006-03-28  1:18               ` regular swsusp flamewar Harald Arnesen
2006-03-28  9:15               ` regular swsusp flamewar [was Re: [PATCH] swsusp: separate swap-writing/reading code] Pavel Machek
2006-03-28  9:16               ` Pavel Machek
2006-03-28 10:28                 ` Nigel Cunningham
2006-03-28  1:16             ` regular swsusp flamewar Harald Arnesen
2006-03-28  9:13               ` Pavel Machek
2006-03-23 23:58     ` [PATCH] swsusp: separate swap-writing/reading code Andrew Morton
2006-03-24  0:32       ` 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=200603240039.42165.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=ncunningham@cyclades.com \
    --cc=pavel@suse.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®