On Tue, Mar 3, 2009 at 1:28 AM, guy keren wrote:
> - Show quoted text -
> Alexander Indenbaum wrote:
>>
>> On Mon, Mar 2, 2009 at 4:44 PM, Valery Reznic
>> wrote:
>>>
>>> --- On Mon, 3/2/09, Alexander Indenbaum
>>> wrote:
>>>
>
Alexander Indenbaum wrote:
On Mon, Mar 2, 2009 at 4:44 PM, Valery Reznic wrote:
--- On Mon, 3/2/09, Alexander Indenbaum wrote:
From: Alexander Indenbaum
Subject: Re: Kernel memory management problem
To: "guy keren"
Cc: "linux-il."
Date: Monday, March 2, 2009, 4:24 PM
--- On Mon, 3/2/09, Alexander Indenbaum wrote:
> From: Alexander Indenbaum
> Subject: Re: Kernel memory management problem
> To: valery_rez...@yahoo.com
> Cc: "linux-il."
> Date: Monday, March 2, 2009, 4:45 PM
> On Mon, Mar 2, 2009 at 4:3
On Mon, Mar 2, 2009 at 5:00 PM, Valery Reznic wrote:
>
> --- On Mon, 3/2/09, Alexander Indenbaum wrote:
>
>> From: Alexander Indenbaum
>> Subject: Re: Kernel memory management problem
>> To: valery_rez...@yahoo.com
>> Cc: "linux-il."
>> Date
>
> Unfortunately this is real problem: if you do something
> like
> while(true) { transfer } then application crashes and burns
> in hell :)
Are you sure that culprit is kernel ?
May be "transfer" part has memory leak ?
Did you try to run it under valgrind ?
or run top ?
> Nondeterministi
On Mon, Mar 2, 2009 at 4:44 PM, Valery Reznic wrote:
>
> --- On Mon, 3/2/09, Alexander Indenbaum wrote:
>
>> From: Alexander Indenbaum
>> Subject: Re: Kernel memory management problem
>> To: "guy keren"
>> Cc: "linux-il."
>> Date: Mo
On Mon, Mar 2, 2009 at 4:35 PM, Valery Reznic wrote:
>>
>> Unfortunately this is real problem: if you do something
>> like
>> while(true) { transfer } then application crashes and burns
>> in hell :)
> Are you sure that culprit is kernel ?
> May be "transfer" part has memory leak ?
>
> Did you try
--- On Mon, 3/2/09, Alexander Indenbaum wrote:
> From: Alexander Indenbaum
> Subject: Re: Kernel memory management problem
> To: "guy keren"
> Cc: "linux-il."
> Date: Monday, March 2, 2009, 4:24 PM
> On Mon, Mar 2, 2009 at 1:16 PM, guy keren
> w
On Mon, Mar 2, 2009 at 1:16 PM, guy keren wrote:
>
> if you don't care about the speed of copying the data and of slowing down
> the disk media consderably during this copying, try to change the copy
> program, so it will use the O_DIRECT flag when opening the file (and then
> you'll need to make
Valery,
See answer inline.
On Mon, Mar 2, 2009 at 1:11 PM, Valery Reznic wrote:
>
> --- On Mon, 3/2/09, Alexander Indenbaum wrote:
>
>>
>> We noticed that if we copy large media file ( 1.4G ) to
>> flash storage
>> filesystem, using wget/sftp/whatever kernel grabs almost
>> all the
>> available
--- On Mon, 3/2/09, Alexander Indenbaum wrote:
>
> We noticed that if we copy large media file ( 1.4G ) to
> flash storage
> filesystem, using wget/sftp/whatever kernel grabs almost
> all the
> available physical memory and buffers are not released
> even after
> transfer is completed and s
if you don't care about the speed of copying the data and of slowing
down the disk media consderably during this copying, try to change the
copy program, so it will use the O_DIRECT flag when opening the file
(and then you'll need to make sure the buffers you pass to write() are
aligned to di
Guys/Girls/Dudes,
I'm working with embedded Linux box powered by 2.4 kernel ( I know :)
we are in process of switching to 2.6 ) with 1G physical memory, no
swap defined and some slow flash storage mounted.
We noticed that if we copy large media file ( 1.4G ) to flash storage
filesystem, using wge
13 matches
Mail list logo
