From: SeongJae Park <sjpark@amazon.com>
To: SeongJae Park <sjpark@amazon.com>
Cc: <davem@davemloft.net>, <viro@zeniv.linux.org.uk>,
<kuba@kernel.org>, <gregkh@linuxfoundation.org>,
<edumazet@google.com>, <sj38.park@gmail.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
SeongJae Park <sjpark@amazon.de>, <snu@amazon.com>,
<amit@kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH net v2 0/2] Revert the 'socket_alloc' life cycle change
Date: Tue, 5 May 2020 13:54:02 +0200 [thread overview]
Message-ID: <20200505115402.25768-1-sjpark@amazon.com> (raw)
In-Reply-To: <20200505081035.7436-1-sjpark@amazon.com> (raw)
CC-ing stable@vger.kernel.org and adding some more explanations.
On Tue, 5 May 2020 10:10:33 +0200 SeongJae Park <sjpark@amazon.com> wrote:
> From: SeongJae Park <sjpark@amazon.de>
>
> The commit 6d7855c54e1e ("sockfs: switch to ->free_inode()") made the
> deallocation of 'socket_alloc' to be done asynchronously using RCU, as
> same to 'sock.wq'. And the following commit 333f7909a857 ("coallocate
> socket_sq with socket itself") made those to have same life cycle.
>
> The changes made the code much more simple, but also made 'socket_alloc'
> live longer than before. For the reason, user programs intensively
> repeating allocations and deallocations of sockets could cause memory
> pressure on recent kernels.
I found this problem on a production virtual machine utilizing 4GB memory while
running lebench[1]. The 'poll big' test of lebench opens 1000 sockets, polls
and closes those. This test is repeated 10,000 times. Therefore it should
consume only 1000 'socket_alloc' objects at once. As size of socket_alloc is
about 800 Bytes, it's only 800 KiB. However, on the recent kernels, it could
consume up to 10,000,000 objects (about 8 GiB). On the test machine, I
confirmed it consuming about 4GB of the system memory and results in OOM.
[1] https://github.com/LinuxPerfStudy/LEBench
>
> To avoid the problem, this commit reverts the changes.
I also tried to make fixup rather than reverts, but I couldn't easily find
simple fixup. As the commits 6d7855c54e1e and 333f7909a857 were for code
refactoring rather than performance optimization, I thought introducing complex
fixup for this problem would make no sense. Meanwhile, the memory pressure
regression could affect real machines. To this end, I decided to quickly
revert the commits first and consider better refactoring later.
Thanks,
SeongJae Park
>
> SeongJae Park (2):
> Revert "coallocate socket_wq with socket itself"
> Revert "sockfs: switch to ->free_inode()"
>
> drivers/net/tap.c | 5 +++--
> drivers/net/tun.c | 8 +++++---
> include/linux/if_tap.h | 1 +
> include/linux/net.h | 4 ++--
> include/net/sock.h | 4 ++--
> net/core/sock.c | 2 +-
> net/socket.c | 23 ++++++++++++++++-------
> 7 files changed, 30 insertions(+), 17 deletions(-)
>
> --
> 2.17.1
next prev parent reply other threads:[~2020-05-05 11:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 8:10 [PATCH net v2 0/2] Revert the 'socket_alloc' life cycle change SeongJae Park
2020-05-05 8:10 ` [PATCH net v2 1/2] Revert "coallocate socket_wq with socket itself" SeongJae Park
2020-05-06 4:55 ` kbuild test robot
2020-05-05 8:10 ` [PATCH net v2 2/2] Revert "sockfs: switch to ->free_inode()" SeongJae Park
2020-05-05 11:54 ` SeongJae Park [this message]
2020-05-05 12:31 ` [PATCH net v2 0/2] Revert the 'socket_alloc' life cycle change Nuernberger, Stefan
2020-05-05 14:53 ` Eric Dumazet
2020-05-05 15:07 ` SeongJae Park
2020-05-05 15:20 ` Eric Dumazet
2020-05-05 15:46 ` SeongJae Park
2020-05-05 16:00 ` Eric Dumazet
2020-05-05 16:13 ` SeongJae Park
2020-05-05 16:25 ` Eric Dumazet
2020-05-05 16:31 ` Eric Dumazet
2020-05-05 16:37 ` Eric Dumazet
2020-05-05 17:05 ` SeongJae Park
2020-05-05 17:30 ` Paul E. McKenney
2020-05-05 17:56 ` SeongJae Park
2020-05-05 18:17 ` Paul E. McKenney
2020-05-05 18:34 ` SeongJae Park
2020-05-05 18:49 ` Paul E. McKenney
2020-05-06 12:59 ` SeongJae Park
2020-05-06 14:33 ` Eric Dumazet
2020-05-06 14:41 ` Paul E. McKenney
2020-05-06 15:20 ` SeongJae Park
2020-05-05 17:28 ` Paul E. McKenney
2020-05-05 18:11 ` SeongJae Park
2020-05-05 17:23 ` Paul E. McKenney
2020-05-05 17:49 ` SeongJae Park
2020-05-05 18:27 ` Paul E. McKenney
2020-05-05 18:40 ` SeongJae Park
2020-05-05 18:48 ` Paul E. McKenney
2020-05-05 16:26 ` Al Viro
2020-05-05 18:48 ` David Miller
2020-05-05 19:00 ` David Miller
2020-05-06 6:24 ` SeongJae Park
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=20200505115402.25768-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=amit@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
--cc=snu@amazon.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).