On Mon, Feb 7, 2011 at 4:59 PM, Wolfgang Denk wrote:
> Dear Lei Wen,
>
> In message you
> wrote:
>>
>> The measurement is simple, for I don't change other part, the heap
>> size and etc part
>> size, but only move the temp buffer to the heap area instead of stack area.
>> So this reduce the larg
Dear Lei Wen,
In message you
wrote:
>
> The measurement is simple, for I don't change other part, the heap
> size and etc part
> size, but only move the temp buffer to the heap area instead of stack area.
> So this reduce the large memory need in the env_relocate_spec() function.
> So that the
Hi Wolfgang,
On Mon, Feb 7, 2011 at 2:58 PM, Wolfgang Denk wrote:
> Dear Lei Wen,
>
> In message you
> wrote:
>>
>> > I mentioned this before: the stack can temporarily use arbitrary
>> > amounts of storage, whil still allowing you to use a maximum of free
>> > RAM at other times.
>> >
>> > I d
Dear Graeme Russ,
In message you
wrote:
>
> > My current implementation is to do a memory dump by using the uboot,
> > while uboot's only task is to compress and write the memory to the sd card.
> > For the compress and write part need a lot of heap, 350k+, if still keep the
> > env buf in the s
Dear Lei Wen,
In message you
wrote:
>
> > I mentioned this before: the stack can temporarily use arbitrary
> > amounts of storage, whil still allowing you to use a maximum of free
> > RAM at other times.
> >
> > I don't really care how much memory is needed on the stack for
> > environment buffe
On Mon, Feb 7, 2011 at 3:38 PM, Lei Wen wrote:
> Hi Wolfgang,
>
> On Mon, Feb 7, 2011 at 12:08 AM, Wolfgang Denk wrote:
>> Dear Lei Wen,
>>
>> In message
>> you wrote:
>>>
> My current implementation is to do a memory dump by using the uboot,
> while uboot's only task is to compress and write
Hi Wolfgang,
On Mon, Feb 7, 2011 at 12:08 AM, Wolfgang Denk wrote:
> Dear Lei Wen,
>
> In message you
> wrote:
>>
>> > malloc arena and stack are adjacent. If you have enough free room in
>> > the malloc arena for the environment buffers, but cannot afford to
>> > have them on your stack, then
Dear Lei Wen,
In message you
wrote:
>
> > malloc arena and stack are adjacent. Â If you have enough free room in
> > the malloc arena for the environment buffers, but cannot afford to
> > have them on your stack, then this means your malloc arena has lots of
> > unused space. Decrease the size
Hi Wolfgang,
On Sat, Feb 5, 2011 at 4:30 PM, Wolfgang Denk wrote:
> Dear Lei Wen,
>
> In message you
> wrote:
>>
>> > In which way do you think this will save any memory?
>>
>> This patch is not intend to save memory...
>
> Then I don't understand at all what the benefit of that patch would
> b
Dear Graeme Russ,
In message <4d4d1987.5010...@gmail.com> you wrote:
>
> Sounds like you have allocated too small a region for your stack - try
> increasing CONFIG_SYS_STACK_SIZE and decreasing CONFIG_SYS_MALLOC_LEN
Most systems don't have anything like CONFIG_SYS_STACK_SIZE; the stack
grows down
On 05/02/11 19:30, Wolfgang Denk wrote:
> Dear Lei Wen,
>
> In message you
> wrote:
>>
>>> In which way do you think this will save any memory?
>>
>> This patch is not intend to save memory...
>
> Then I don't understand at all what the benefit of that patch would
> be.
>
>> One of our project
Dear Lei Wen,
In message you
wrote:
>
> > In which way do you think this will save any memory?
>
> This patch is not intend to save memory...
Then I don't understand at all what the benefit of that patch would
be.
> One of our project need to confine the ddr usage of uboot in the smallest
>
Hi Wolfgang,
On Sat, Feb 5, 2011 at 5:18 AM, Wolfgang Denk wrote:
> Dear Lei Wen,
>
> In message <1296788903-7604-1-git-send-email-lei...@marvell.com> you wrote:
>> Original env buf directly locate at stack lead large stack footprint
>> when call those env functions. It is not good when the syste
Dear Lei Wen,
In message <1296788903-7604-1-git-send-email-lei...@marvell.com> you wrote:
> Original env buf directly locate at stack lead large stack footprint
> when call those env functions. It is not good when the system memory
> is critical or only want the uboot run at restrict range, that i
On Fri, 4 Feb 2011 11:08:23 +0800
Lei Wen wrote:
> Original env buf directly locate at stack lead large stack footprint
> when call those env functions. It is not good when the system memory
> is critical or only want the uboot run at restrict range, that is not
> to touch the memory of other pla
Original env buf directly locate at stack lead large stack footprint
when call those env functions. It is not good when the system memory
is critical or only want the uboot run at restrict range, that is not
to touch the memory of other place at its best.
So now this patch move the env buf to the
16 matches
Mail list logo
