All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taz <rastataz@gmail.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Fancontrol memory consumption
Date: Mon, 02 Mar 2015 11:05:09 +0000	[thread overview]
Message-ID: <54F443E5.1040802@gmail.com> (raw)
In-Reply-To: <20141105175729.39a88ab1@endymion.delvare>

Le 02/03/2015 11:30, Jean Delvare a écrit :
> On Thu, 13 Nov 2014 15:36:32 +0100, Taz wrote:
>> (sorry I just saw my reply still was in my drafts, don't know why...)
>>
>> Indeed : my current bash version is 4.3.11
>> Although I don't have line 585 in my fancontrol script
>> I can apply the the patch (lines 497 & 536 for fancontrol v0.7)
>>
>> I also gave it a try without the wait lines and not sending to
>> background the previous
>> sleep command the wait was waiting for anyway (useless ?)
>>
>> => Mem consumption seems to be the same in all cases, we'll see in the
>> long run...
> BTW, can you please tell me
> * Which architecture this is (x86 or x86-64)?
> * The value of "ulimit -u" on this system.
> * The total amount of memory on the system.
>
> As Chet Ramey explained to me, the memory consumption is bound and the
> default limit depends on these factors. Assuming an x86-64 system,
> eating 22 MB of memory as you reported would take about 734000 records
> of 32 bytes each, and "ulimit -u" would be set to that value by default
> for a system with about 187 GB of memory. Which I would not expect in a
> NAS, so something is wrong.
>

The hardware is actually a ReadyNAS ultra 6000 with 2GB RAM.
I'm running a x86_64 ubuntu server 14.04 with 3.16 SMP kernel
and fancontrol from standard repos (pkg vers is 1:3.3.4-2ubuntu1).

=======

\x12(root@ReadyNAS:pts/0)\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12# 
ulimit -u
     7892

(root@ReadyNAS:pts/0)\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12\x12#free
                  total       used       free     shared buffers     cached
     Mem:       2039828    1829656     210172        708 4796    1091516
     -/+ buffers/cache:     733344    1306484
     Swap:      5242876          0    5242876


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2015-03-02 11:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05 16:57 [lm-sensors] Fancontrol memory consumption Jean Delvare
2014-11-07  9:15 ` Jean Delvare
2014-11-13 14:36 ` Taz
2015-02-28 10:14 ` Jean Delvare
2015-02-28 12:39 ` Taz
2015-02-28 13:13 ` Taz
2015-03-02  7:39 ` Jean Delvare
2015-03-02 10:30 ` Jean Delvare
2015-03-02 11:05 ` Taz [this message]
2015-03-02 12:26 ` Jean Delvare
2015-03-02 18:10 ` Taz
2015-06-01 13:32 ` Jean Delvare
2015-06-01 14:47 ` Jean Delvare
2015-06-13 18:17 ` Taz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54F443E5.1040802@gmail.com \
    --to=rastataz@gmail.com \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.