public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [patch 00/26] Dynamic kernel command-line
@ 2007-01-18 12:58 Bernhard Walle
  2007-01-18 12:59 ` [patch 19/26] Dynamic kernel command-line - sh Bernhard Walle
  0 siblings, 1 reply; 6+ messages in thread
From: Bernhard Walle @ 2007-01-18 12:58 UTC (permalink / raw)
  To: linux-kernel

This patch has already been posted by Alon Bar-Lev <alon.barlev@gmail.com>
in 2nd Dec 2006. He didn't get any response.  Because I think that this
patch would be really useful being able to increase the command line, I
post this patch again to get some response.

This patches are against 2.6.20-rc4-mm1.

Current implementation stores a static command-line buffer allocated to
COMMAND_LINE_SIZE size. Most architectures stores two copies of this
buffer, one for future reference and one for parameter parsing.

Current kernel command-line size for most architecture is much too small
for module parameters, video settings, initramfs parameters and much
more. The problem is that setting COMMAND_LINE_SIZE to a grater value,
allocates static buffers.

In order to allow a greater command-line size, these buffers should be
dynamically allocated or marked as init disposable buffers, so unused
memory can be released.

This patch renames the static saved_command_line variable into
boot_command_line adding __initdata attribute, so that it can be
disposed after initialization. This rename is required so applications
that use saved_command_line will not be affected by this change.

It reintroduces saved_command_line as dynamically allocated buffer to
match the data in boot_command_line.

It also mark secondary command-line buffer as __initdata, and copies it
to dynamically allocated static_command_line buffer components may hold
reference to it after initialization.

This patch is for linux-2.6.19 and is divided to target each
architecture. I could not check this in any architecture so please
forgive me if I got it wrong.

The per-architecture modification is very simple, use boot_command_line
in place of saved_command_line. The common code is the change into
dynamic command-line.

Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>


^ permalink raw reply	[flat|nested] 6+ messages in thread
* [PATCH 00/26] Dynamic kernel command-line
@ 2006-12-02 10:47 Alon Bar-Lev
  2006-12-02 10:55 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
  0 siblings, 1 reply; 6+ messages in thread
From: Alon Bar-Lev @ 2006-12-02 10:47 UTC (permalink / raw)
  To: linux-arch, linux-kernel


Hello,

This is take 3 of submission, I submit this patch
once in a few monthes to collect some more signatures :)
Until now, I got three:
- avr32
- sh
- sh64

I know this is not one of major priorities, but it
should be simple enough to be reviewed and included.

I will also be happy to get a REJECT response, so I
stop trying to get it included. Any suggestions of
how to push this farward will also be appreciated.

Current implementation stores a static command-line
buffer allocated to COMMAND_LINE_SIZE size. Most
architectures stores two copies of this buffer, one
for future reference and one for parameter parsing.

Current kernel command-line size for most architecture
is much too small for module parameters, video settings,
initramfs paramters and much more. The problem is that
setting COMMAND_LINE_SIZE to a grater value, allocates
static buffers.

In order to allow a greater command-line size, these
buffers should be dynamically allocated or marked
as init disposable buffers, so unused memory can be
released.

This patch renames the static saved_command_line
variable into boot_command_line adding __initdata
attribute, so that it can be disposed after
initialization. This rename is required so applications
that use saved_command_line will not be affected
by this change.

It reintroduces saved_command_line as dynamically
allocated buffer to match the data in boot_command_line.

It also mark secondary command-line buffer as __initdata,
and copies it to dynamically allocated static_command_line
buffer components may hold reference to it after
initialization.

This patch is for linux-2.6.19 and is divided to
target each architecture. I could not check this in any
architecture so please forgive me if I got it wrong.

The per-architecture modification is very simple, use
boot_command_line in place of saved_command_line. The
common code is the change into dynamic command-line.

Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>

---


^ permalink raw reply	[flat|nested] 6+ messages in thread
* [PATCH 00/26] Dynamic kernel command-line - Resend please ignore last
@ 2006-09-03 22:15 Alon Bar-Lev
  2006-09-03 22:22 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
  0 siblings, 1 reply; 6+ messages in thread
From: Alon Bar-Lev @ 2006-09-03 22:15 UTC (permalink / raw)
  To: Alon Bar-Lev, Andi Kleen, Matt Domsch, Andrew Morton,
	linux-kernel, johninsd, davej, Riley, trini, davem, ecd, jj,
	anton, wli, lethal, lethal, rc, spyro, spyro, rth, avr32,
	hskinnemoen, starvik, ralf, matthew, grundler, geert, zippel,
	paulus, schwidefsky, heiko.carstens, uclinux-v850, chris


Current implementation stores a static command-line
buffer allocated to COMMAND_LINE_SIZE size. Most
architectures stores two copies of this buffer, one
for future reference and one for parameter parsing.

In order to allow a greater command-line size, these
buffers should be dynamically allocated or marked
as init disposable buffers, so unused memory can be
released.

This patch renames the static saved_command_line
variable into boot_command_line adding __initdata
attribute, so that it can be disposed after
initialization. This rename is required so applications
that use saved_command_line will not be affected
by this change.

It reintroduces saved_command_line as dynamically
allocated buffer to match the data in boot_command_line.

It also mark secondary command-line buffer as __initdata,
and copies it to dynamically allocated static_command_line
buffer components may hold reference to it after
initialization.

This patch is for linux-2.6.18-rc5-mm1 and is divided to
target each architecture. I could not check this in any
architecture so please forgive me if I got it wrong.

Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>

---

-- 
VGER BF report: H 0

^ permalink raw reply	[flat|nested] 6+ messages in thread
* [PATCH 00/26] Dynamic kernel command-line
@ 2006-09-03 21:50 Alon Bar-Lev
  2006-09-03 22:01 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
  0 siblings, 1 reply; 6+ messages in thread
From: Alon Bar-Lev @ 2006-09-03 21:50 UTC (permalink / raw)
  To: Alon Bar-Lev, Andi Kleen, Matt Domsch, Andrew Morton,
	linux-kernel, johninsd, davej, Riley, trini, davem, ecd, jj,
	anton, wli, lethal, lethal, rc, spyro, spyro, rth, avr32,
	hskinnemoen, starvik, ralf, matthew, grundler, geert, zippel,
	paulus, schwidefsky, heiko.carstens, uclinux-v850, chris


Current implementation stores a static command-line
buffer allocated to COMMAND_LINE_SIZE size. Most
architectures stores two copies of this buffer, one
for future reference and one for parameter parsing.

In order to allow a greater command-line size, these
buffers should be dynamically allocated or marked
as init disposable buffers, so unused memory can be
released.

This patch renames the static saved_command_line
variable into boot_command_line adding __initdata
attribute, so that it can be disposed after
initialization. This rename is required so applications
that use saved_command_line will not be affected
by this change.

It reintroduces saved_command_line as dynamically
allocated buffer to match the data in boot_command_line.

It also mark secondary command-line buffer as __initdata,
and copies it to dynamically allocated static_command_line
buffer components may hold reference to it after
initialization.

This patch is for linux-2.6.18-rc5-mm1 and is divided to
target each architecture. I could not check this in any
architecture so please forgive me if I got it wrong.

Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>

---

-- 
VGER BF report: U 0.5

^ permalink raw reply	[flat|nested] 6+ messages in thread
end of thread, other threads:[~2007-01-18 13:04 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <200610112111.02040.alon.barlev@gmail.com>
     [not found] ` <200610112117.10698.alon.barlev@gmail.com>
     [not found]   ` <200610112116.56120.alon.barlev@gmail.com>
2006-10-12  8:16     ` [PATCH 19/26] Dynamic kernel command-line - sh Paul Mundt
2006-10-12  8:30       ` Alon Bar-Lev
2007-01-18 12:58 [patch 00/26] Dynamic kernel command-line Bernhard Walle
2007-01-18 12:59 ` [patch 19/26] Dynamic kernel command-line - sh Bernhard Walle
  -- strict thread matches above, loose matches on Subject: below --
2006-12-02 10:47 [PATCH 00/26] Dynamic kernel command-line Alon Bar-Lev
2006-12-02 10:55 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
2006-09-03 22:15 [PATCH 00/26] Dynamic kernel command-line - Resend please ignore last Alon Bar-Lev
2006-09-03 22:22 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev
2006-09-03 21:50 [PATCH 00/26] Dynamic kernel command-line Alon Bar-Lev
2006-09-03 22:01 ` [PATCH 19/26] Dynamic kernel command-line - sh Alon Bar-Lev

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox