License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 14:07:57 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0
|
2008-10-15 19:50:22 +00:00
|
|
|
#include <linux/fs.h>
|
|
|
|
|
#include <linux/init.h>
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
|
#include <linux/mm.h>
|
2013-11-14 22:31:02 +00:00
|
|
|
#include <linux/hugetlb.h>
|
2008-10-15 19:50:22 +00:00
|
|
|
#include <linux/mman.h>
|
|
|
|
|
#include <linux/mmzone.h>
|
2023-03-21 10:34:30 +00:00
|
|
|
#include <linux/memblock.h>
|
2008-10-15 19:50:22 +00:00
|
|
|
#include <linux/proc_fs.h>
|
2018-08-22 04:53:58 +00:00
|
|
|
#include <linux/percpu.h>
|
2008-10-15 19:50:22 +00:00
|
|
|
#include <linux/seq_file.h>
|
|
|
|
|
#include <linux/swap.h>
|
|
|
|
|
#include <linux/vmstat.h>
|
2011-07-26 23:09:06 +00:00
|
|
|
#include <linux/atomic.h>
|
2013-04-29 22:07:28 +00:00
|
|
|
#include <linux/vmalloc.h>
|
fs/proc/meminfo.c: include cma info in proc/meminfo
This patch include CMA info (CMATotal, CMAFree) in /proc/meminfo.
Currently, in a CMA enabled system, if somebody wants to know the total
CMA size declared, there is no way to tell, other than the dmesg or
/var/log/messages logs.
With this patch we are showing the CMA info as part of meminfo, so that it
can be determined at any point of time. This will be populated only when
CMA is enabled.
Below is the sample output from a ARM based device with RAM:512MB and CMA:16MB.
MemTotal: 471172 kB
MemFree: 111712 kB
MemAvailable: 271172 kB
.
.
.
CmaTotal: 16384 kB
CmaFree: 6144 kB
This patch also fix below checkpatch errors that were found during these changes.
ERROR: space required after that ',' (ctx:ExV)
199: FILE: fs/proc/meminfo.c:199:
+ ,atomic_long_read(&num_poisoned_pages) << (PAGE_SHIFT - 10)
^
ERROR: space required after that ',' (ctx:ExV)
202: FILE: fs/proc/meminfo.c:202:
+ ,K(global_page_state(NR_ANON_TRANSPARENT_HUGEPAGES) *
^
ERROR: space required after that ',' (ctx:ExV)
206: FILE: fs/proc/meminfo.c:206:
+ ,K(totalcma_pages)
^
total: 3 errors, 0 warnings, 2 checks, 236 lines checked
Signed-off-by: Pintu Kumar <pintu.k@samsung.com>
Signed-off-by: Vishnu Pratap Singh <vishnu.ps@samsung.com>
Acked-by: Michal Nazarewicz <mina86@mina86.com>
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-12-19 00:17:18 +00:00
|
|
|
#ifdef CONFIG_CMA
|
|
|
|
|
#include <linux/cma.h>
|
|
|
|
|
#endif
|
2023-07-17 16:02:27 +00:00
|
|
|
#include <linux/zswap.h>
|
2008-10-15 19:50:22 +00:00
|
|
|
#include <asm/page.h>
|
|
|
|
|
#include "internal.h"
|
|
|
|
|
|
|
|
|
|
void __attribute__((weak)) arch_report_meminfo(struct seq_file *m)
|
|
|
|
|
{
|
|
|
|
|
}
|
|
|
|
|
|
2016-10-08 00:02:23 +00:00
|
|
|
static void show_val_kb(struct seq_file *m, const char *s, unsigned long num)
|
|
|
|
|
{
|
2018-04-10 23:31:16 +00:00
|
|
|
seq_put_decimal_ull_width(m, s, num << (PAGE_SHIFT - 10), 8);
|
2016-10-08 00:02:23 +00:00
|
|
|
seq_write(m, " kB\n", 4);
|
|
|
|
|
}
|
|
|
|
|
|
2008-10-15 19:50:22 +00:00
|
|
|
static int meminfo_proc_show(struct seq_file *m, void *v)
|
|
|
|
|
{
|
|
|
|
|
struct sysinfo i;
|
|
|
|
|
unsigned long committed;
|
|
|
|
|
long cached;
|
/proc/meminfo: provide estimated available memory
Many load balancing and workload placing programs check /proc/meminfo to
estimate how much free memory is available. They generally do this by
adding up "free" and "cached", which was fine ten years ago, but is
pretty much guaranteed to be wrong today.
It is wrong because Cached includes memory that is not freeable as page
cache, for example shared memory segments, tmpfs, and ramfs, and it does
not include reclaimable slab memory, which can take up a large fraction
of system memory on mostly idle systems with lots of files.
Currently, the amount of memory that is available for a new workload,
without pushing the system into swap, can be estimated from MemFree,
Active(file), Inactive(file), and SReclaimable, as well as the "low"
watermarks from /proc/zoneinfo.
However, this may change in the future, and user space really should not
be expected to know kernel internals to come up with an estimate for the
amount of free memory.
It is more convenient to provide such an estimate in /proc/meminfo. If
things change in the future, we only have to change it in one place.
Signed-off-by: Rik van Riel <riel@redhat.com>
Reported-by: Erik Mouw <erik.mouw_2@nxp.com>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-01-21 23:49:05 +00:00
|
|
|
long available;
|
2008-10-15 19:50:22 +00:00
|
|
|
unsigned long pages[NR_LRU_LISTS];
|
2018-10-26 22:05:50 +00:00
|
|
|
unsigned long sreclaimable, sunreclaim;
|
2008-10-15 19:50:22 +00:00
|
|
|
int lru;
|
|
|
|
|
|
|
|
|
|
si_meminfo(&i);
|
|
|
|
|
si_swapinfo(&i);
|
proc/meminfo: avoid open coded reading of vm_committed_as
Patch series "make vm_committed_as_batch aware of vm overcommit policy", v6.
When checking a performance change for will-it-scale scalability mmap test
[1], we found very high lock contention for spinlock of percpu counter
'vm_committed_as':
94.14% 0.35% [kernel.kallsyms] [k] _raw_spin_lock_irqsave
48.21% _raw_spin_lock_irqsave;percpu_counter_add_batch;__vm_enough_memory;mmap_region;do_mmap;
45.91% _raw_spin_lock_irqsave;percpu_counter_add_batch;__do_munmap;
Actually this heavy lock contention is not always necessary. The
'vm_committed_as' needs to be very precise when the strict
OVERCOMMIT_NEVER policy is set, which requires a rather small batch number
for the percpu counter.
So keep 'batch' number unchanged for strict OVERCOMMIT_NEVER policy, and
enlarge it for not-so-strict OVERCOMMIT_ALWAYS and OVERCOMMIT_GUESS
policies.
Benchmark with the same testcase in [1] shows 53% improvement on a 8C/16T
desktop, and 2097%(20X) on a 4S/72C/144T server. And for that case,
whether it shows improvements depends on if the test mmap size is bigger
than the batch number computed.
We tested 10+ platforms in 0day (server, desktop and laptop). If we lift
it to 64X, 80%+ platforms show improvements, and for 16X lift, 1/3 of the
platforms will show improvements.
And generally it should help the mmap/unmap usage,as Michal Hocko
mentioned:
: I believe that there are non-synthetic worklaods which would benefit
: from a larger batch. E.g. large in memory databases which do large
: mmaps during startups from multiple threads.
Note: There are some style complain from checkpatch for patch 4, as sysctl
handler declaration follows the similar format of sibling functions
[1] https://lore.kernel.org/lkml/20200305062138.GI5972@shao2-debian/
This patch (of 4):
Use the existing vm_memory_committed() instead, which is also convenient
for future change.
Signed-off-by: Feng Tang <feng.tang@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Acked-by: Michal Hocko <mhocko@suse.com>
Cc: Matthew Wilcox (Oracle) <willy@infradead.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Mel Gorman <mgorman@suse.de>
Cc: Qian Cai <cai@lca.pw>
Cc: Kees Cook <keescook@chromium.org>
Cc: Andi Kleen <andi.kleen@intel.com>
Cc: Tim Chen <tim.c.chen@intel.com>
Cc: Dave Hansen <dave.hansen@intel.com>
Cc: Huang Ying <ying.huang@intel.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: Dennis Zhou <dennis@kernel.org>
Cc: Haiyang Zhang <haiyangz@microsoft.com>
Cc: kernel test robot <rong.a.chen@intel.com>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: Tejun Heo <tj@kernel.org>
Link: http://lkml.kernel.org/r/1594389708-60781-1-git-send-email-feng.tang@intel.com
Link: http://lkml.kernel.org/r/1594389708-60781-2-git-send-email-feng.tang@intel.com
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2020-08-07 06:23:03 +00:00
|
|
|
committed = vm_memory_committed();
|
2008-10-15 19:50:22 +00:00
|
|
|
|
2016-07-28 22:46:20 +00:00
|
|
|
cached = global_node_page_state(NR_FILE_PAGES) -
|
2013-02-23 00:34:37 +00:00
|
|
|
total_swapcache_pages() - i.bufferram;
|
2008-10-15 19:50:22 +00:00
|
|
|
if (cached < 0)
|
|
|
|
|
cached = 0;
|
|
|
|
|
|
|
|
|
|
for (lru = LRU_BASE; lru < NR_LRU_LISTS; lru++)
|
2016-08-11 22:32:57 +00:00
|
|
|
pages[lru] = global_node_page_state(NR_LRU_BASE + lru);
|
2008-10-15 19:50:22 +00:00
|
|
|
|
2016-03-17 21:19:05 +00:00
|
|
|
available = si_mem_available();
|
2020-08-07 06:20:39 +00:00
|
|
|
sreclaimable = global_node_page_state_pages(NR_SLAB_RECLAIMABLE_B);
|
|
|
|
|
sunreclaim = global_node_page_state_pages(NR_SLAB_UNRECLAIMABLE_B);
|
/proc/meminfo: provide estimated available memory
Many load balancing and workload placing programs check /proc/meminfo to
estimate how much free memory is available. They generally do this by
adding up "free" and "cached", which was fine ten years ago, but is
pretty much guaranteed to be wrong today.
It is wrong because Cached includes memory that is not freeable as page
cache, for example shared memory segments, tmpfs, and ramfs, and it does
not include reclaimable slab memory, which can take up a large fraction
of system memory on mostly idle systems with lots of files.
Currently, the amount of memory that is available for a new workload,
without pushing the system into swap, can be estimated from MemFree,
Active(file), Inactive(file), and SReclaimable, as well as the "low"
watermarks from /proc/zoneinfo.
However, this may change in the future, and user space really should not
be expected to know kernel internals to come up with an estimate for the
amount of free memory.
It is more convenient to provide such an estimate in /proc/meminfo. If
things change in the future, we only have to change it in one place.
Signed-off-by: Rik van Riel <riel@redhat.com>
Reported-by: Erik Mouw <erik.mouw_2@nxp.com>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-01-21 23:49:05 +00:00
|
|
|
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "MemTotal: ", i.totalram);
|
|
|
|
|
show_val_kb(m, "MemFree: ", i.freeram);
|
|
|
|
|
show_val_kb(m, "MemAvailable: ", available);
|
|
|
|
|
show_val_kb(m, "Buffers: ", i.bufferram);
|
|
|
|
|
show_val_kb(m, "Cached: ", cached);
|
|
|
|
|
show_val_kb(m, "SwapCached: ", total_swapcache_pages());
|
|
|
|
|
show_val_kb(m, "Active: ", pages[LRU_ACTIVE_ANON] +
|
|
|
|
|
pages[LRU_ACTIVE_FILE]);
|
|
|
|
|
show_val_kb(m, "Inactive: ", pages[LRU_INACTIVE_ANON] +
|
|
|
|
|
pages[LRU_INACTIVE_FILE]);
|
|
|
|
|
show_val_kb(m, "Active(anon): ", pages[LRU_ACTIVE_ANON]);
|
|
|
|
|
show_val_kb(m, "Inactive(anon): ", pages[LRU_INACTIVE_ANON]);
|
|
|
|
|
show_val_kb(m, "Active(file): ", pages[LRU_ACTIVE_FILE]);
|
|
|
|
|
show_val_kb(m, "Inactive(file): ", pages[LRU_INACTIVE_FILE]);
|
|
|
|
|
show_val_kb(m, "Unevictable: ", pages[LRU_UNEVICTABLE]);
|
2017-09-06 23:23:36 +00:00
|
|
|
show_val_kb(m, "Mlocked: ", global_zone_page_state(NR_MLOCK));
|
2016-10-08 00:02:23 +00:00
|
|
|
|
2008-10-15 19:50:22 +00:00
|
|
|
#ifdef CONFIG_HIGHMEM
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "HighTotal: ", i.totalhigh);
|
|
|
|
|
show_val_kb(m, "HighFree: ", i.freehigh);
|
|
|
|
|
show_val_kb(m, "LowTotal: ", i.totalram - i.totalhigh);
|
|
|
|
|
show_val_kb(m, "LowFree: ", i.freeram - i.freehigh);
|
2009-01-08 12:04:47 +00:00
|
|
|
#endif
|
2016-10-08 00:02:23 +00:00
|
|
|
|
2009-01-08 12:04:47 +00:00
|
|
|
#ifndef CONFIG_MMU
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "MmapCopy: ",
|
|
|
|
|
(unsigned long)atomic_long_read(&mmap_pages_allocated));
|
2008-10-15 19:50:22 +00:00
|
|
|
#endif
|
2016-10-08 00:02:23 +00:00
|
|
|
|
|
|
|
|
show_val_kb(m, "SwapTotal: ", i.totalswap);
|
|
|
|
|
show_val_kb(m, "SwapFree: ", i.freeswap);
|
2022-05-19 21:08:53 +00:00
|
|
|
#ifdef CONFIG_ZSWAP
|
mm: zswap: optimize zswap pool size tracking
Profiling the munmap() of a zswapped memory region shows 60% of the total
cycles currently going into updating the zswap_pool_total_size.
There are three consumers of this counter:
- store, to enforce the globally configured pool limit
- meminfo & debugfs, to report the size to the user
- shrink, to determine the batch size for each cycle
Instead of aggregating everytime an entry enters or exits the zswap
pool, aggregate the value from the zpools on-demand:
- Stores aggregate the counter anyway upon success. Aggregating to
check the limit instead is the same amount of work.
- Meminfo & debugfs might benefit somewhat from a pre-aggregated
counter, but aren't exactly hotpaths.
- Shrinking can aggregate once for every cycle instead of doing it for
every freed entry. As the shrinker might work on tens or hundreds of
objects per scan cycle, this is a large reduction in aggregations.
The paths that benefit dramatically are swapin, swapoff, and unmaps.
There could be millions of pages being processed until somebody asks for
the pool size again. This eliminates the pool size updates from those
paths entirely.
Top profile entries for a 24G range munmap(), before:
38.54% zswap-unmap [kernel.kallsyms] [k] zs_zpool_total_size
12.51% zswap-unmap [kernel.kallsyms] [k] zpool_get_total_size
9.10% zswap-unmap [kernel.kallsyms] [k] zswap_update_total_size
2.95% zswap-unmap [kernel.kallsyms] [k] obj_cgroup_uncharge_zswap
2.88% zswap-unmap [kernel.kallsyms] [k] __slab_free
2.86% zswap-unmap [kernel.kallsyms] [k] xas_store
and after:
7.70% zswap-unmap [kernel.kallsyms] [k] __slab_free
7.16% zswap-unmap [kernel.kallsyms] [k] obj_cgroup_uncharge_zswap
6.74% zswap-unmap [kernel.kallsyms] [k] xas_store
It was also briefly considered to move to a single atomic in zswap
that is updated by the backends, since zswap only cares about the sum
of all pools anyway. However, zram directly needs per-pool information
out of zsmalloc. To keep the backend from having to update two atomics
every time, I opted for the lazy aggregation instead for now.
Link: https://lkml.kernel.org/r/20240312153901.3441-1-hannes@cmpxchg.org
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Yosry Ahmed <yosryahmed@google.com>
Reviewed-by: Chengming Zhou <chengming.zhou@linux.dev>
Reviewed-by: Nhat Pham <nphamcs@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2024-03-12 15:34:11 +00:00
|
|
|
show_val_kb(m, "Zswap: ", zswap_total_pages());
|
2022-05-19 21:08:53 +00:00
|
|
|
seq_printf(m, "Zswapped: %8lu kB\n",
|
|
|
|
|
(unsigned long)atomic_read(&zswap_stored_pages) <<
|
|
|
|
|
(PAGE_SHIFT - 10));
|
|
|
|
|
#endif
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "Dirty: ",
|
|
|
|
|
global_node_page_state(NR_FILE_DIRTY));
|
|
|
|
|
show_val_kb(m, "Writeback: ",
|
|
|
|
|
global_node_page_state(NR_WRITEBACK));
|
|
|
|
|
show_val_kb(m, "AnonPages: ",
|
|
|
|
|
global_node_page_state(NR_ANON_MAPPED));
|
|
|
|
|
show_val_kb(m, "Mapped: ",
|
|
|
|
|
global_node_page_state(NR_FILE_MAPPED));
|
|
|
|
|
show_val_kb(m, "Shmem: ", i.sharedram);
|
2018-10-26 22:05:50 +00:00
|
|
|
show_val_kb(m, "KReclaimable: ", sreclaimable +
|
|
|
|
|
global_node_page_state(NR_KERNEL_MISC_RECLAIMABLE));
|
|
|
|
|
show_val_kb(m, "Slab: ", sreclaimable + sunreclaim);
|
|
|
|
|
show_val_kb(m, "SReclaimable: ", sreclaimable);
|
|
|
|
|
show_val_kb(m, "SUnreclaim: ", sunreclaim);
|
2016-10-08 00:02:23 +00:00
|
|
|
seq_printf(m, "KernelStack: %8lu kB\n",
|
2020-08-07 06:21:37 +00:00
|
|
|
global_node_page_state(NR_KERNEL_STACK_KB));
|
2020-04-27 16:00:08 +00:00
|
|
|
#ifdef CONFIG_SHADOW_CALL_STACK
|
|
|
|
|
seq_printf(m, "ShadowCallStack:%8lu kB\n",
|
2020-08-07 06:21:37 +00:00
|
|
|
global_node_page_state(NR_KERNEL_SCS_KB));
|
2020-04-27 16:00:08 +00:00
|
|
|
#endif
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "PageTables: ",
|
2020-12-15 03:07:17 +00:00
|
|
|
global_node_page_state(NR_PAGETABLE));
|
2022-11-17 04:32:47 +00:00
|
|
|
show_val_kb(m, "SecPageTables: ",
|
mm: add NR_SECONDARY_PAGETABLE to count secondary page table uses.
We keep track of several kernel memory stats (total kernel memory, page
tables, stack, vmalloc, etc) on multiple levels (global, per-node,
per-memcg, etc). These stats give insights to users to how much memory
is used by the kernel and for what purposes.
Currently, memory used by KVM mmu is not accounted in any of those
kernel memory stats. This patch series accounts the memory pages
used by KVM for page tables in those stats in a new
NR_SECONDARY_PAGETABLE stat. This stat can be later extended to account
for other types of secondary pages tables (e.g. iommu page tables).
KVM has a decent number of large allocations that aren't for page
tables, but for most of them, the number/size of those allocations
scales linearly with either the number of vCPUs or the amount of memory
assigned to the VM. KVM's secondary page table allocations do not scale
linearly, especially when nested virtualization is in use.
From a KVM perspective, NR_SECONDARY_PAGETABLE will scale with KVM's
per-VM pages_{4k,2m,1g} stats unless the guest is doing something
bizarre (e.g. accessing only 4kb chunks of 2mb pages so that KVM is
forced to allocate a large number of page tables even though the guest
isn't accessing that much memory). However, someone would need to either
understand how KVM works to make that connection, or know (or be told) to
go look at KVM's stats if they're running VMs to better decipher the stats.
Furthermore, having NR_PAGETABLE side-by-side with NR_SECONDARY_PAGETABLE
is informative. For example, when backing a VM with THP vs. HugeTLB,
NR_SECONDARY_PAGETABLE is roughly the same, but NR_PAGETABLE is an order
of magnitude higher with THP. So having this stat will at the very least
prove to be useful for understanding tradeoffs between VM backing types,
and likely even steer folks towards potential optimizations.
The original discussion with more details about the rationale:
https://lore.kernel.org/all/87ilqoi77b.wl-maz@kernel.org
This stat will be used by subsequent patches to count KVM mmu
memory usage.
Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
Acked-by: Shakeel Butt <shakeelb@google.com>
Acked-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20220823004639.2387269-2-yosryahmed@google.com
Signed-off-by: Sean Christopherson <seanjc@google.com>
2022-08-23 00:46:36 +00:00
|
|
|
global_node_page_state(NR_SECONDARY_PAGETABLE));
|
2016-10-08 00:02:23 +00:00
|
|
|
|
2020-06-02 04:48:21 +00:00
|
|
|
show_val_kb(m, "NFS_Unstable: ", 0);
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "Bounce: ",
|
2017-09-06 23:23:36 +00:00
|
|
|
global_zone_page_state(NR_BOUNCE));
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "WritebackTmp: ",
|
|
|
|
|
global_node_page_state(NR_WRITEBACK_TEMP));
|
|
|
|
|
show_val_kb(m, "CommitLimit: ", vm_commit_limit());
|
|
|
|
|
show_val_kb(m, "Committed_AS: ", committed);
|
|
|
|
|
seq_printf(m, "VmallocTotal: %8lu kB\n",
|
|
|
|
|
(unsigned long)VMALLOC_TOTAL >> 10);
|
2019-07-12 04:00:13 +00:00
|
|
|
show_val_kb(m, "VmallocUsed: ", vmalloc_nr_pages());
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "VmallocChunk: ", 0ul);
|
2018-08-22 04:53:58 +00:00
|
|
|
show_val_kb(m, "Percpu: ", pcpu_nr_pages());
|
2016-10-08 00:02:23 +00:00
|
|
|
|
2023-08-08 03:33:59 +00:00
|
|
|
memtest_report_meminfo(m);
|
2023-03-21 10:34:30 +00:00
|
|
|
|
2009-09-16 09:50:15 +00:00
|
|
|
#ifdef CONFIG_MEMORY_FAILURE
|
2016-10-08 00:02:23 +00:00
|
|
|
seq_printf(m, "HardwareCorrupted: %5lu kB\n",
|
|
|
|
|
atomic_long_read(&num_poisoned_pages) << (PAGE_SHIFT - 10));
|
2011-01-13 23:46:58 +00:00
|
|
|
#endif
|
2016-10-08 00:02:23 +00:00
|
|
|
|
2011-01-13 23:46:58 +00:00
|
|
|
#ifdef CONFIG_TRANSPARENT_HUGEPAGE
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "AnonHugePages: ",
|
2021-02-24 20:03:23 +00:00
|
|
|
global_node_page_state(NR_ANON_THPS));
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "ShmemHugePages: ",
|
2021-02-24 20:03:31 +00:00
|
|
|
global_node_page_state(NR_SHMEM_THPS));
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "ShmemPmdMapped: ",
|
2021-02-24 20:03:35 +00:00
|
|
|
global_node_page_state(NR_SHMEM_PMDMAPPED));
|
2019-10-19 03:20:27 +00:00
|
|
|
show_val_kb(m, "FileHugePages: ",
|
2021-02-24 20:03:27 +00:00
|
|
|
global_node_page_state(NR_FILE_THPS));
|
2019-10-19 03:20:27 +00:00
|
|
|
show_val_kb(m, "FilePmdMapped: ",
|
2021-02-24 20:03:39 +00:00
|
|
|
global_node_page_state(NR_FILE_PMDMAPPED));
|
fs/proc/meminfo.c: include cma info in proc/meminfo
This patch include CMA info (CMATotal, CMAFree) in /proc/meminfo.
Currently, in a CMA enabled system, if somebody wants to know the total
CMA size declared, there is no way to tell, other than the dmesg or
/var/log/messages logs.
With this patch we are showing the CMA info as part of meminfo, so that it
can be determined at any point of time. This will be populated only when
CMA is enabled.
Below is the sample output from a ARM based device with RAM:512MB and CMA:16MB.
MemTotal: 471172 kB
MemFree: 111712 kB
MemAvailable: 271172 kB
.
.
.
CmaTotal: 16384 kB
CmaFree: 6144 kB
This patch also fix below checkpatch errors that were found during these changes.
ERROR: space required after that ',' (ctx:ExV)
199: FILE: fs/proc/meminfo.c:199:
+ ,atomic_long_read(&num_poisoned_pages) << (PAGE_SHIFT - 10)
^
ERROR: space required after that ',' (ctx:ExV)
202: FILE: fs/proc/meminfo.c:202:
+ ,K(global_page_state(NR_ANON_TRANSPARENT_HUGEPAGES) *
^
ERROR: space required after that ',' (ctx:ExV)
206: FILE: fs/proc/meminfo.c:206:
+ ,K(totalcma_pages)
^
total: 3 errors, 0 warnings, 2 checks, 236 lines checked
Signed-off-by: Pintu Kumar <pintu.k@samsung.com>
Signed-off-by: Vishnu Pratap Singh <vishnu.ps@samsung.com>
Acked-by: Michal Nazarewicz <mina86@mina86.com>
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-12-19 00:17:18 +00:00
|
|
|
#endif
|
2016-10-08 00:02:23 +00:00
|
|
|
|
fs/proc/meminfo.c: include cma info in proc/meminfo
This patch include CMA info (CMATotal, CMAFree) in /proc/meminfo.
Currently, in a CMA enabled system, if somebody wants to know the total
CMA size declared, there is no way to tell, other than the dmesg or
/var/log/messages logs.
With this patch we are showing the CMA info as part of meminfo, so that it
can be determined at any point of time. This will be populated only when
CMA is enabled.
Below is the sample output from a ARM based device with RAM:512MB and CMA:16MB.
MemTotal: 471172 kB
MemFree: 111712 kB
MemAvailable: 271172 kB
.
.
.
CmaTotal: 16384 kB
CmaFree: 6144 kB
This patch also fix below checkpatch errors that were found during these changes.
ERROR: space required after that ',' (ctx:ExV)
199: FILE: fs/proc/meminfo.c:199:
+ ,atomic_long_read(&num_poisoned_pages) << (PAGE_SHIFT - 10)
^
ERROR: space required after that ',' (ctx:ExV)
202: FILE: fs/proc/meminfo.c:202:
+ ,K(global_page_state(NR_ANON_TRANSPARENT_HUGEPAGES) *
^
ERROR: space required after that ',' (ctx:ExV)
206: FILE: fs/proc/meminfo.c:206:
+ ,K(totalcma_pages)
^
total: 3 errors, 0 warnings, 2 checks, 236 lines checked
Signed-off-by: Pintu Kumar <pintu.k@samsung.com>
Signed-off-by: Vishnu Pratap Singh <vishnu.ps@samsung.com>
Acked-by: Michal Nazarewicz <mina86@mina86.com>
Cc: Rafael Aquini <aquini@redhat.com>
Cc: Jerome Marchand <jmarchan@redhat.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2014-12-19 00:17:18 +00:00
|
|
|
#ifdef CONFIG_CMA
|
2016-10-08 00:02:23 +00:00
|
|
|
show_val_kb(m, "CmaTotal: ", totalcma_pages);
|
|
|
|
|
show_val_kb(m, "CmaFree: ",
|
2017-09-06 23:23:36 +00:00
|
|
|
global_zone_page_state(NR_FREE_CMA_PAGES));
|
2009-09-16 09:50:15 +00:00
|
|
|
#endif
|
2008-10-15 19:50:22 +00:00
|
|
|
|
2023-06-06 14:26:29 +00:00
|
|
|
#ifdef CONFIG_UNACCEPTED_MEMORY
|
|
|
|
|
show_val_kb(m, "Unaccepted: ",
|
|
|
|
|
global_zone_page_state(NR_UNACCEPTED));
|
|
|
|
|
#endif
|
|
|
|
|
|
2008-10-15 19:50:22 +00:00
|
|
|
hugetlb_report_meminfo(m);
|
|
|
|
|
|
|
|
|
|
arch_report_meminfo(m);
|
|
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static int __init proc_meminfo_init(void)
|
|
|
|
|
{
|
2022-09-20 17:35:23 +00:00
|
|
|
struct proc_dir_entry *pde;
|
|
|
|
|
|
|
|
|
|
pde = proc_create_single("meminfo", 0, NULL, meminfo_proc_show);
|
|
|
|
|
pde_make_permanent(pde);
|
2008-10-15 19:50:22 +00:00
|
|
|
return 0;
|
|
|
|
|
}
|
2014-01-23 23:55:45 +00:00
|
|
|
fs_initcall(proc_meminfo_init);
|
