All of lore.kernel.org
 help / color / mirror / Atom feed
From: bruno_vidal@hp.com
To: Matthew Wilcox <willy@debian.org>,
	"parisc-linux@lists.parisc-linux.org"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] struct page: page in use or not ?
Date: Thu, 20 Mar 2003 12:23:08 +0100	[thread overview]
Message-ID: <3E79A49C.81C188AA@hp.com> (raw)
In-Reply-To: 20030319170749.GX14520@parcelfarce.linux.theplanet.co.uk

[-- Attachment #1: Type: text/plain, Size: 1839 bytes --]

    Hi
What do you mean by "swsusp" patche ? What it do....
Actually I'm looking at the kmalloc() function in order to
understand how it determine the bucket, and so to know
which pages I need to dump before I can use the page structure.
Do you think it is a good starting point, or using page
struture is really a bad option ?

    Thanks.

Matthew Wilcox wrote:

> On Wed, Mar 19, 2003 at 05:50:46PM +0100, bruno_vidal@hp.com wrote:
> >     Hi
> > I'm currently trying to reduce the dump time, and then I try to dump only
> > pages that are currently use by the system. In page structure I found a flag,
> > I was thinking a good one for this purpose:
> > atomic_t count;                 /* Usage count, see below. */
> >
> > But after taking only pages where count != 0, something was broken, I was
> > not able to look at proc structure, and several things.....
> > If a do a "full" dump I'm still able to look at what I need, so this page.count
> > is not accurate for this purpose. So does't exist a good way to know if a page
> > is in use or not ?
>
> The problem is multi-page allocs.  The `struct page' is not valid
> for those.  I'm not sure what a good way of doing this is -- have you
> looked at the swsusp patches to see how they do it?
>
> --
> "It's not Hollywood.  War is real, war is primarily not about defeat or
> victory, it is about death.  I've seen thousands and thousands of dead bodies.
> Do you think I want to have an academic debate on this subject?" -- Robert Fisk
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

--
        Vidal Bruno, (770-4271)
        SSD-HA Team, HP-UX & LINUX Support
        bruno_vidal@admin.france.hp.com



[-- Attachment #2: Card for --]
[-- Type: text/x-vcard, Size: 386 bytes --]

begin:vcard 
n:Bruno;VIDAL
tel;fax:01-69-82-60-14
tel;work:01-69-29-42-71
x-mozilla-html:TRUE
url:www.france.hp.com
org:Solution Center
version:2.1
email;internet:bruno_vidal@hp.com
title:Expert Logiciel Environnement Haute Disponibilité
adr;quoted-printable:;;HP France=0D=0A;Z.A de Courtaboeuf;1 Av. du Canada;91947 Les Ulis cedex;France
x-mozilla-cpt:;26208
fn:VIDAL Bruno
end:vcard

  reply	other threads:[~2003-03-20 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 16:50 [parisc-linux] struct page: page in use or not ? bruno_vidal
2003-03-19 17:03 ` Randolph Chung
2003-03-19 17:07 ` Matthew Wilcox
2003-03-20 11:23   ` bruno_vidal [this message]
2003-03-20 12:13     ` Matthew Wilcox
2003-03-20 15:39     ` Michael Wood

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=3E79A49C.81C188AA@hp.com \
    --to=bruno_vidal@hp.com \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=willy@debian.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.