[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: GNU Parallel Bug Reports Problems with --memfree option
|
From: |
Ole Tange |
|
Subject: |
Re: GNU Parallel Bug Reports Problems with --memfree option |
|
Date: |
Thu, 13 Aug 2015 21:37:06 +0200 |
On Thu, Aug 13, 2015 at 11:06 AM, Andreas Bernauer
<address@hidden> wrote:
> Looks as if --memfree should parse /proc/meminfo directly (instead of
> the output of 'free', which parses /proc/meminfo). The meminfo format
> looks easily grepable.
Do we know how old Linux kernels' /proc/meminfo are formatted, so we
do not break old systems just to support new ones.
I think it should be MemFree + Buffers + Cached + SwapCached.
ssh server "awk '/^((Swap)?Cached|MemFree|Buffers):/ { sum += \$2}
END { print sum }' /proc/meminfo "
> Further, I'm wondering why parallel is grepping the buffers/cache line
> instead of the 'free' column...
It looks at the free column AND at the buffers/cache line.
total used free shared buffers cached
Mem: 32765028 32362040 402988 1063944 207564 11111620
-/+ buffers/cache: 21042856 11722172
Swap: 38920180 22764 38897416
On this system GNU Parallel should find 11 G free, and not 0.4 G. The same here:
total used free shared buffers cached
Mem: 32765028 22627852 10137176 1077844 3296 1428504
-/+ buffers/cache: 21196052 11568976
Swap: 38920180 22764 38897416
/Ole