From: liuxp11@chinatelecom.cn <liuxp11@chinatelecom.cn>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] syscalls/ioctl: ioctl_sg01.c: ioctl_sg01 invoked oom-killer
Date: Wed, 27 Jan 2021 18:04:35 +0800 [thread overview]
Message-ID: <2021012718043566596022@chinatelecom.cn> (raw)
In-Reply-To: YBE03REJywKIlM0X@yuki.lan
[root@test-env-nm05-compute-14e5e72e38 ~]# cat /proc/meminfo
MemTotal: 526997420 kB
MemFree: 520224908 kB
MemAvailable: 519936744 kB
Buffers: 0 kB
Cached: 2509036 kB
SwapCached: 0 kB
Active: 906868 kB
Inactive: 2398084 kB
Active(anon): 816396 kB
Inactive(anon): 77236 kB
Active(file): 90472 kB
Inactive(file): 2320848 kB
Unevictable: 610056 kB
Mlocked: 610056 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 1406336 kB
Mapped: 118628 kB
Shmem: 84400 kB
KReclaimable: 193752 kB
Slab: 703668 kB
SReclaimable: 193752 kB
SUnreclaim: 509916 kB
KernelStack: 12672 kB
PageTables: 14056 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 263498708 kB
Committed_AS: 10263760 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 651756 kB
VmallocChunk: 0 kB
Percpu: 62464 kB
HardwareCorrupted: 88 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
CmaTotal: 0 kB
CmaFree: 0 kB
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Hugetlb: 0 kB
DirectMap4k: 1371808 kB
DirectMap2M: 49661952 kB
DirectMap1G: 486539264 kB
[root@test-env-nm05-compute-14e5e72e38 ~]# cat /proc/sys/vm/min_free_kbytes
90112
From: Cyril Hrubis
Date: 2021-01-27 17:39
To: Xinpeng Liu
CC: ltp
Subject: Re: [LTP] [PATCH 1/2] syscalls/ioctl: ioctl_sg01.c: ioctl_sg01 invoked oom-killer
Hi!
> MemTotal: 198101744 kB
> MemFree: 189303148 kB
> MemAvailable: 188566732 kB
This sounds really strange, usually MemFree is smaller than MemAvailable
since MemFree does not include page cache.
Is this freshly booted system?
Can you send the whole meminfo here please?
--
Cyril Hrubis
chrubis@suse.cz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210127/d67a18b3/attachment.htm>
next prev parent reply other threads:[~2021-01-27 10:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 10:24 [LTP] [PATCH 1/2] syscalls/ioctl: ioctl_sg01.c: ioctl_sg01 invoked oom-killer Xinpeng Liu
2021-01-25 10:24 ` [LTP] [PATCH 2/2] syscalls/ioctl: ioctl_sg01.c:TBROK: Test killed! Xinpeng Liu
2021-01-27 4:41 ` Li Wang
2021-01-27 4:27 ` [LTP] [PATCH 1/2] syscalls/ioctl: ioctl_sg01.c: ioctl_sg01 invoked oom-killer Li Wang
2021-01-27 5:42 ` liuxp11
2021-01-27 6:54 ` liuxp11
2021-01-27 7:58 ` Li Wang
2021-01-27 8:05 ` Li Wang
2021-01-27 9:24 ` Cyril Hrubis
2021-01-27 10:03 ` Li Wang
2021-01-27 8:49 ` liuxp11
2021-01-27 9:50 ` Cyril Hrubis
2021-01-27 9:39 ` Cyril Hrubis
2021-01-27 9:53 ` Martin Doucha
2021-01-27 10:07 ` liuxp11
2021-01-27 10:04 ` liuxp11 [this message]
2021-01-27 11:28 ` Martin Doucha
2021-01-27 11:41 ` liuxp11
2021-01-27 11:46 ` Martin Doucha
2021-01-27 11:50 ` liuxp11
2021-03-04 7:52 ` Li Wang
2021-03-05 5:52 ` liuxp11
2021-03-05 9:02 ` Li Wang
2021-03-24 9:26 ` liuxp11
2021-04-11 5:01 ` Li Wang
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=2021012718043566596022@chinatelecom.cn \
--to=liuxp11@chinatelecom.cn \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox