From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Andrew Morton <akpm@digeo.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Don't refill pcp lists during SWSUSP.
Date: Tue, 18 Mar 2003 17:27:02 +1200 [thread overview]
Message-ID: <1047965222.2430.3.camel@laptop-linux.cunninghams> (raw)
In-Reply-To: <20030317160556.4efc880f.akpm@digeo.com>
On Tue, 2003-03-18 at 12:05, Andrew Morton wrote:
> Nigel Cunningham <ncunningham@clear.net.nz> wrote:
> >
> > +extern unsigned int suspend_task;
>
>
> Please do:
>
> #ifdef CONFIG_SOFTWARE_SUSPEND
> unsigned int suspend_task;
> #else
> #define suspend_task 0
> #endif
>
> so the compiler can remove the few fast-path instructions which you have
> added.
Okee doke. Will do.
I said I was going to use dynamically allocated bitmaps instead of page
flags. Do you mind if I do use pageflags after all (at least for the
moment)? I've used one in the generate_free_page_map patch, and need one
more to mark pages which will be saved in another pageset.
> >
> > + suspend_task = current->pid;
> > +
>
> Zero is a valid PID (the idle task...). It might be clearer to make
> suspend_task a task_struct*.
Mmm, but I will use suspend_task elsewhere and wanted to make the test
simple (zero = not suspending at the moment; since init will never be
the suspend task, it's safe usage).
Regards,
Nigel
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
Be diligent to present yourself approved to God as a workman who does
not need to be ashamed, handling accurately the word of truth.
-- 2 Timothy 2:14, NASB.
next prev parent reply other threads:[~2003-03-18 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 23:56 [PATCH] Don't refill pcp lists during SWSUSP Nigel Cunningham
2003-03-18 0:05 ` Andrew Morton
2003-03-18 5:27 ` Nigel Cunningham [this message]
[not found] ` <20030317222018.5c7f7a56.akpm@digeo.com>
2003-03-18 6:35 ` Nigel Cunningham
2003-03-18 6:40 ` Nigel Cunningham
2003-03-18 8:18 ` Pavel Machek
2003-03-18 10:06 ` Nigel Cunningham
2003-03-18 16:58 ` Pavel Machek
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=1047965222.2430.3.camel@laptop-linux.cunninghams \
--to=ncunningham@clear.net.nz \
--cc=akpm@digeo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.