| To: | dmitri.vorobiev@gmail.com |
|---|---|
| Subject: | Re: COMMAND_LINE_SIZE and CONFIG_FRAME_WARN |
| From: | Atsushi Nemoto <anemo@mba.ocn.ne.jp> |
| Date: | Sun, 08 Nov 2009 02:19:14 +0900 (JST) |
| Cc: | macro@linux-mips.org, ddaney@caviumnetworks.com, linux-mips@linux-mips.org |
| In-reply-to: | <90edad820911061017y373cf1ale5f10b742d633b7d@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <90edad820911060923w6cd59c5dh57d123b6bc9d4219@mail.gmail.com> <alpine.LFD.2.00.0911061726150.9725@eddie.linux-mips.org> <90edad820911061017y373cf1ale5f10b742d633b7d@mail.gmail.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
On Fri, 6 Nov 2009 20:17:06 +0200, Dmitri Vorobiev <dmitri.vorobiev@gmail.com> wrote: > I believe that Atsushi-san was talking about the MIPS code only. > Indeed, he mentioned CL_SIZE, which used to be a MIPS-specific alias > to COMMAND_LINE_SIZE. Yes, and I think static array is safest option now. MIPS might be able to use large stack on early bootstrap stage, but this assumption looks slightly fragile for me. And excessive zero-initialized __initdata size will not be a problem especially if vmlinux is compressed. Thank you everyone, I will post a patch soon. --- Atsushi Nemoto |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH -queue v1 4/7] [loongson] lemote-2f: add pci support, Wu Zhangjin |
|---|---|
| Next by Date: | [PATCH] MIPS: Make local arrays with CL_SIZE static __initdata, Atsushi Nemoto |
| Previous by Thread: | Re: COMMAND_LINE_SIZE and CONFIG_FRAME_WARN, Dmitri Vorobiev |
| Next by Thread: | Re: COMMAND_LINE_SIZE and CONFIG_FRAME_WARN, Maciej W. Rozycki |
| Indexes: | [Date] [Thread] [Top] [All Lists] |