From: Stephen Hemminger <stephen@networkplumber.org>
To: sgarzare@redhat.com
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 215329] New: The vsock component triggers out of memory when sending small packets.
Date: Wed, 15 Dec 2021 07:38:36 -0800 [thread overview]
Message-ID: <20211215073807.30c0041d@hermes.local> (raw)
Begin forwarded message:
Date: Wed, 15 Dec 2021 03:40:59 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 215329] New: The vsock component triggers out of memory when sending small packets.
https://bugzilla.kernel.org/show_bug.cgi?id=215329
Bug ID: 215329
Summary: The vsock component triggers out of memory when
sending small packets.
Product: Networking
Version: 2.5
Kernel Version: 4.19.90
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: kircherlike@outlook.com
Regression: No
The memory usage of the vsock component when sending small packets is much
higher than that when sending large packets. When the VM memory is
insufficient, the out of memory is triggered.
Server（host）：iperf3 --vsock -s 2
Client（guest）：iperf3 --vsock -c 2 -t 10000 -l 1 -P 100
Slab information of kernel kmalloc in the 1 KB data packet is sent. The values
of kmalloc-256 and kmalloc-4096 are significantly higher than those in the
normal environment.
Traffic sending environment:
kmalloc-8192 68 68 8192 4 8 : tunables 0 0 0 : slabdata 17 17 0
kmalloc-4096 1186 1224 4096 8 8 : tunables 0 0 0 : slabdata 153 153 0
kmalloc-2048 965 992 2048 16 8 : tunables 0 0 0 : slabdata 62 62 0
kmalloc-1024 967 1040 1024 16 4 : tunables 0 0 0 : slabdata 65 65 0
kmalloc-512 1120 1120 512 16 2 : tunables 0 0 0 : slabdata 70 70 0
kmalloc-256 19644992 19644992 256 16 1 : tunables 0 0 0 : slabdata 1227812
1227812 0
kmalloc-128 760027 762656 128 32 1 : tunables 0 0 0 : slabdata 23833 23833 0
Normal environment:
kmalloc-8192 68 68 8192 4 8 : tunables 0 0 0 : slabdata 17 17 0
kmalloc-4096 1248 1248 4096 8 8 : tunables 0 0 0 : slabdata 156 156 0
kmalloc-2048 1008 1040 2048 16 8 : tunables 0 0 0 : slabdata 65 65 0
kmalloc-1024 948 960 1024 16 4 : tunables 0 0 0 : slabdata 60 60 0
kmalloc-512 1072 1072 512 16 2 : tunables 0 0 0 : slabdata 67 67 0
kmalloc-256 3199 3264 256 16 1 : tunables 0 0 0 : slabdata 204 204 0
kmalloc-128 761575 762080 128 32 1 : tunables 0 0 0 : slabdata 23815 23815 0
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2021-12-15 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 15:38 Stephen Hemminger [this message]
2021-12-15 16:45 ` Fw: [Bug 215329] New: The vsock component triggers out of memory when sending small packets Stefano Garzarella
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=20211215073807.30c0041d@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
/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.