public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Michael Neuling <mikey@neuling.org>
Cc: linux-kernel@vger.kernel.org, H Peter Anvin <hpa@zytor.com>,
	Andrew Morton <akpm@osdl.org>, Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [PATCH] Add retain_initrd boot option
Date: Wed, 06 Dec 2006 21:39:42 -0800	[thread overview]
Message-ID: <4577A91E.70501@oracle.com> (raw)
In-Reply-To: <20614.1165469597@neuling.org>

Michael Neuling wrote:
> Add retain_initrd option to control freeing of initrd memory after
> extraction.  By default, free memory as previously. 
> 
> The first boot will need to hold a copy of the in memory fs for the
> second boot.  This image can be large (much larger than the kernel),
> hence we can save time when the memory loader is slow.  Also, it reduces
> the memory footprint while extracting the first boot since you don't
> need another copy of the fs.
> 
> Signed-off-by: Michael Neuling <mikey@neuling.org>
> ---
> Removed unnecessary init of do_retain_initrd as suggested by Randy
> Dunlap.
> 
>  Documentation/kernel-parameters.txt |    2 ++
>  init/initramfs.c                    |   18 ++++++++++++++++--
>  2 files changed, 18 insertions(+), 2 deletions(-)
> 
> Index: linux-2.6-ozlabs/Documentation/kernel-parameters.txt
> ===================================================================
> --- linux-2.6-ozlabs.orig/Documentation/kernel-parameters.txt
> +++ linux-2.6-ozlabs/Documentation/kernel-parameters.txt
> @@ -1366,6 +1366,8 @@ and is between 256 and 4096 characters. 
>  	resume=		[SWSUSP]
>  			Specify the partition device for software suspend
>  
> +	retain_initrd	[RAM] Keep initrd memory after extraction
> +
>  	rhash_entries=	[KNL,NET]
>  			Set number of hash buckets for route cache
>  
> Index: linux-2.6-ozlabs/init/initramfs.c
> ===================================================================
> --- linux-2.6-ozlabs.orig/init/initramfs.c
> +++ linux-2.6-ozlabs/init/initramfs.c
> @@ -487,6 +487,17 @@ static char * __init unpack_to_rootfs(ch
>  	return message;
>  }
>  
> +static int do_retain_initrd;
> +
> +static int __init retain_initrd_param(char *str)
> +{
> +	if (*str)
> +		return 0;
> +	do_retain_initrd = 1;
> +	return 1;
> +}
> +__setup("retain_initrd", retain_initrd_param);
> +
>  extern char __initramfs_start[], __initramfs_end[];
>  #ifdef CONFIG_BLK_DEV_INITRD
>  #include <linux/initrd.h>
> @@ -494,10 +505,13 @@ extern char __initramfs_start[], __initr
>  
>  static void __init free_initrd(void)
>  {
> -#ifdef CONFIG_KEXEC
>  	unsigned long crashk_start = (unsigned long)__va(crashk_res.start);
>  	unsigned long crashk_end   = (unsigned long)__va(crashk_res.end);

I'm still not seeing how using crashk_res is valid here when
CONFIG_KEXEC=n.  Can you explain that, please?
You did test this with KEXEC=y and KEXEC=n, right?

> +	if (do_retain_initrd)
> +		goto skip;
> +
> +#ifdef CONFIG_KEXEC
>  	/*
>  	 * If the initrd region is overlapped with crashkernel reserved region,
>  	 * free only memory that is not part of crashkernel region.
> @@ -515,7 +529,7 @@ static void __init free_initrd(void)
>  	} else
>  #endif
>  		free_initrd_mem(initrd_start, initrd_end);
> -
> +skip:
>  	initrd_start = 0;
>  	initrd_end = 0;
>  }


-- 
~Randy

  reply	other threads:[~2006-12-07  5:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07  5:33 [PATCH] Add retain_initrd boot option Michael Neuling
2006-12-07  5:39 ` Randy Dunlap [this message]
2006-12-07  5:54   ` Michael Neuling
  -- strict thread matches above, loose matches on Subject: below --
2006-12-07  5:57 Michael Neuling

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=4577A91E.70501@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@osdl.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikey@neuling.org \
    --cc=viro@ftp.linux.org.uk \
    /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