linux-mips
[Top] [All Lists]

Re: COMMAND_LINE_SIZE and CONFIG_FRAME_WARN

To: Dmitri Vorobiev <dmitri.vorobiev@gmail.com>
Subject: Re: COMMAND_LINE_SIZE and CONFIG_FRAME_WARN
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Fri, 6 Nov 2009 17:30:53 +0000 (GMT)
Cc: David Daney <ddaney@caviumnetworks.com>, Atsushi Nemoto <anemo@mba.ocn.ne.jp>, linux-mips@linux-mips.org
In-reply-to: <90edad820911060923w6cd59c5dh57d123b6bc9d4219@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20091107.010839.246840249.anemo@mba.ocn.ne.jp> <90edad820911060822g40233a8ft28001d68186b989e@mail.gmail.com> <90edad820911060834t5c14aa30t847c3b75bf7e36e@mail.gmail.com> <4AF4526B.3020502@caviumnetworks.com> <90edad820911060907j4a605167xfe1ebdf0dcf7b635@mail.gmail.com> <alpine.LFD.2.00.0911061710160.9725@eddie.linux-mips.org> <90edad820911060923w6cd59c5dh57d123b6bc9d4219@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Alpine 2.00 (LFD 1167 2008-08-23)
On Fri, 6 Nov 2009, Dmitri Vorobiev wrote:

> >  KSEG space is not paged, so who cares about the page size?  You're not
> > making additional stack page allocations, although you can overflow the
> > space available at some point (but that's avoided if you know a priori
> > your backtrace is not going to be deep).  Static allocation has its
> > drawbacks, for example it takes storage space (if it's initialised data)
> > or memory space (if it's BSS) indefinitely.
> 
> Thanks for the explanation. Then a variable-size array, I guess.

 Note that MIPS is at an advantage here and other architectures may have 
to page the kernel space, so the observation is valid for our platform 
code only -- for generic code (anything that goes outside arch/mips) you 
may have to change the assumptions.

  Maciej

<Prev in Thread] Current Thread [Next in Thread>