mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: akpm@digeo.com
Subject: Re: [PATCH] mark shrinkable slabs as being reclaimable
Date: Tue, 27 May 2003 23:31:02 +0100	[thread overview]
Message-ID: <1054074662.26966.4.camel@imladris.demon.co.uk> (raw)
In-Reply-To: <200305252319.h4PNJkpJ027852@hera.kernel.org>

On Sun, 2003-05-25 at 23:11, Linux Kernel Mailing List wrote:
> ChangeSet 1.1308, 2003/05/25 15:11:47-07:00, akpm@digeo.com
> 
> 	[PATCH] mark shrinkable slabs as being reclaimable
> 	
> 	All slabs which can be reclaimed via VM presure are marked as being
> 	shrinkable, so the core slab code will keep count of their pages.

If my understanding of this is correct -- stuff that will be freed on
prune_icache() or other memory pressure should be marked such -- then...

> diff -Nru a/fs/jffs/inode-v23.c b/fs/jffs/inode-v23.c
> --- a/fs/jffs/inode-v23.c	Sun May 25 16:19:51 2003
> +++ b/fs/jffs/inode-v23.c	Sun May 25 16:19:51 2003
> @@ -1806,9 +1806,11 @@
>  	jffs_proc_root = proc_mkdir("jffs", proc_root_fs);
>  #endif
>  	fm_cache = kmem_cache_create("jffs_fm", sizeof(struct jffs_fm),
> -				     0, SLAB_HWCACHE_ALIGN, NULL, NULL);
> +				     0, SLAB_HWCACHE_ALIGN|SLAB_RECLAIM_ACCOUNT, 
> +				     NULL, NULL);

No.

>  	node_cache = kmem_cache_create("jffs_node",sizeof(struct jffs_node),
> -				       0, SLAB_HWCACHE_ALIGN, NULL, NULL);
> +				       0, SLAB_HWCACHE_ALIGN|SLAB_RECLAIM_ACCOUNT, 
> +				       NULL, NULL);

No.

> diff -Nru a/fs/jffs2/malloc.c b/fs/jffs2/malloc.c
> --- a/fs/jffs2/malloc.c	Sun May 25 16:19:51 2003
> +++ b/fs/jffs2/malloc.c	Sun May 25 16:19:51 2003
> @@ -73,7 +73,8 @@
>  
>  	inode_cache_slab = kmem_cache_create("jffs2_inode_cache",
>  					     sizeof(struct jffs2_inode_cache),
> -					     0, JFFS2_SLAB_POISON, NULL, NULL);
> +					     0, JFFS2_SLAB_POISON|SLAB_RECLAIM_ACCOUNT, 
> +					     NULL, NULL);

No.

> --- a/fs/jffs2/super.c	Sun May 25 16:19:51 2003
> +++ b/fs/jffs2/super.c	Sun May 25 16:19:51 2003
> @@ -299,7 +299,7 @@
>  
>  	jffs2_inode_cachep = kmem_cache_create("jffs2_i",
>  					     sizeof(struct jffs2_inode_info),
> -					     0, SLAB_HWCACHE_ALIGN,
> +					     0, SLAB_HWCACHE_ALIGN|SLAB_RECLAIM_ACCOUNT,
>  					     jffs2_i_init_once, NULL);

Yes.

-- 
dwmw2



       reply	other threads:[~2003-05-27 22:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200305252319.h4PNJkpJ027852@hera.kernel.org>
2003-05-27 22:31 ` David Woodhouse [this message]
2003-05-27 22:38   ` 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=1054074662.26966.4.camel@imladris.demon.co.uk \
    --to=dwmw2@infradead.org \
    --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 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®