linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"lse-tech@lists.sourceforge.net" <lse-tech@lists.sourceforge.net>
Subject: Re: 2.5.35-mm1
Date: Wed, 18 Sep 2002 23:54:24 +0200	[thread overview]
Message-ID: <20020918215424.GB2967@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <3D88F099.81A50A89@digeo.com>

Hi!

> > > url: http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.35/2.5.35-mm1/
> > >
> > > Significant rework of the new sleep/wakeup code - make it look totally
> > > different from the current APIs to avoid confusion, and to make it
> > > simpler to use.
> > 
> > Did you add any hooks to allow me to free memory for swsusp?
> 
> I just did then.  You'll need to call
> 
> 	freed = shrink_all_memory(99);

Thanx a lot.

> to free up 99 pages.  It returns the number which it actually
> freed.  If that's not 99 then it's time to give up.  There is
> no oom-killer in this code path.

So... I'll do something like shrink_all_memory(1000000) and it will
free as much as possible, right?

> I haven't tested it yet.  And it's quite a long way back in the
> queue I'm afraid - it has a dependency chain, and I prefer to

So if I apply this to my tree it will not work (that's what
"dependency chain means", right?). Okay, thanx anyway.

> send stuff to Linus which has been tested for a couple of weeks, and
> hasn't changed for one week.
> 
> Can you use the allocate-lots-then-free-it trick in the meanwhile?

In the meanwhile, swsusp only working when there's lot of ram is
probably okay. As IDE patch is not in, swsusp is dangerous, anyway.

									Pavel 

> --- 2.5.36/mm/vmscan.c~swsusp-feature	Wed Sep 18 13:55:20 2002
> +++ 2.5.36-akpm/mm/vmscan.c	Wed Sep 18 14:29:13 2002
> @@ -694,12 +694,19 @@ try_to_free_pages(struct zone *classzone
>  }
>  
>  /*
> - * kswapd will work across all this node's zones until they are all at
> - * pages_high.
> + * For kswapd, balance_pgdat() will work across all this node's zones until
> + * they are all at pages_high.
> + *
> + * If `nr_pages' is non-zero then it is the number of pages which are to be
> + * reclaimed, regardless of the zone occupancies.  This is a software suspend
> + * special.
> + *
> + * Returns the number of pages which were actually freed.
>   */
> -static void kswapd_balance_pgdat(pg_data_t *pgdat)
> +static int balance_pgdat(pg_data_t *pgdat, int nr_pages)
>  {
> -	int priority = DEF_PRIORITY;
> +	int to_free = nr_pages;
> +	int priority;
>  	int i;
>  
>  	for (priority = DEF_PRIORITY; priority; priority--) {
> @@ -712,13 +719,15 @@ static void kswapd_balance_pgdat(pg_data
>  			int to_reclaim;
>  
>  			to_reclaim = zone->pages_high - zone->free_pages;
> +			if (nr_pages && to_free > 0)
> +				to_reclaim = min(to_free, SWAP_CLUSTER_MAX*8);
>  			if (to_reclaim <= 0)
>  				continue;
>  			success = 0;
>  			max_scan = zone->nr_inactive >> priority;
>  			if (max_scan < to_reclaim * 2)
>  				max_scan = to_reclaim * 2;
> -			shrink_zone(zone, max_scan, GFP_KSWAPD,
> +			to_free -= shrink_zone(zone, max_scan, GFP_KSWAPD,
>  					to_reclaim, &nr_mapped);
>  			shrink_slab(max_scan + nr_mapped, GFP_KSWAPD);
>  		}
> @@ -726,6 +735,7 @@ static void kswapd_balance_pgdat(pg_data
>  			break;	/* All zones are at pages_high */
>  		blk_congestion_wait(WRITE, HZ/4);
>  	}
> +	return nr_pages - to_free;
>  }
>  
>  /*
> @@ -772,10 +782,34 @@ int kswapd(void *p)
>  		prepare_to_wait(&pgdat->kswapd_wait, &wait, TASK_INTERRUPTIBLE);
>  		schedule();
>  		finish_wait(&pgdat->kswapd_wait, &wait);
> -		kswapd_balance_pgdat(pgdat);
> +		balance_pgdat(pgdat, 0);
>  		blk_run_queues();
>  	}
>  }
> +
> +#ifdef CONFIG_SOFTWARE_SUSPEND
> +/*
> + * Try to free `nr_pages' of memory, system-wide.  Returns the number of freed
> + * pages.
> + */
> +int shrink_all_memory(int nr_pages)
> +{
> +	pg_data_t *pgdat;
> +	int nr_to_free = nr_pages;
> +	int ret = 0;
> +
> +	for_each_pgdat(pgdat) {
> +		int freed;
> +
> +		freed = balance_pgdat(pgdat, nr_to_free);
> +		ret += freed;
> +		nr_to_free -= freed;
> +		if (nr_to_free <= 0)
> +			break;
> +	}
> +	return ret;
> +}
> +#endif
>  
>  static int __init kswapd_init(void)
>  {
> --- 2.5.36/include/linux/swap.h~swsusp-feature	Wed Sep 18 14:03:01 2002
> +++ 2.5.36-akpm/include/linux/swap.h	Wed Sep 18 14:16:29 2002
> @@ -163,6 +163,7 @@ extern void swap_setup(void);
>  
>  /* linux/mm/vmscan.c */
>  extern int try_to_free_pages(struct zone *, unsigned int, unsigned int);
> +int shrink_all_memory(int nr_pages);
>  
>  /* linux/mm/page_io.c */
>  int swap_readpage(struct file *file, struct page *page);
> 
> .

-- 
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.

  reply	other threads:[~2002-09-18 21:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16  7:15 2.5.35-mm1 Andrew Morton
2002-09-17 16:07 ` 2.5.35-mm1 Pavel Machek
2002-09-18 21:31   ` 2.5.35-mm1 Andrew Morton
2002-09-18 21:54     ` Pavel Machek [this message]
2002-09-19  7:51 ` 2.5.35-mm1 Daniel Phillips
2002-09-19  8:19   ` 2.5.35-mm1 Andrew Morton

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=20020918215424.GB2967@atrey.karlin.mff.cuni.cz \
    --to=pavel@suse.cz \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).