From: Glauber Costa <glommer@parallels.com>
To: davem@davemloft.net
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
cgroups@vger.kernel.org
Subject: [PATCH 0/2] Proposed fixes for tcp memory pressure
Date: Thu, 15 Dec 2011 13:34:30 +0400 [thread overview]
Message-ID: <1323941672-14324-1-git-send-email-glommer@parallels.com> (raw)
Hi,
I propose the following two fixes for the issues we're having in
linux-next.
The first one just moves the definition out of the CONFIG_INET,
and should fix the compile problems with allnoconfig.
The second one is a bit bigger, and takes away the socket
registration functions. As I've explained in the Changelog,
I believe this to be the saner way to do it. We need to do allocations
in both create and init time.
This was compile tested with 4 different randconfigs, CGROUPS off,
KMEM cgroup off, INET off, all them on, and boot tested with
everything on.
Thanks.
Glauber Costa (2):
Move limit definitions outside CONFIG_INET
Explicitly call tcp creation and init from memcontrol.c
include/linux/memcontrol.h | 2 +-
include/net/sock.h | 2 --
include/net/tcp_memcontrol.h | 19 ++++++++++++++++++-
mm/memcontrol.c | 13 ++++---------
net/core/sock.c | 37 -------------------------------------
net/ipv4/tcp_memcontrol.c | 11 ++++++-----
6 files changed, 29 insertions(+), 55 deletions(-)
--
1.7.6.4
next reply other threads:[~2011-12-15 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 9:34 Glauber Costa [this message]
2011-12-15 9:34 ` [PATCH 1/2] Move limit definitions outside CONFIG_INET Glauber Costa
2011-12-15 16:59 ` David Miller
2011-12-15 9:34 ` [PATCH 2/2] Explicitly call tcp creation and init from memcontrol.c Glauber Costa
2011-12-15 16:13 ` KAMEZAWA Hiroyuki
2011-12-15 16:18 ` Glauber Costa
2011-12-15 16:57 ` David Miller
2011-12-15 22:20 ` KAMEZAWA Hiroyuki
2011-12-16 2:06 ` Glauber Costa
2011-12-15 17:00 ` David Miller
2011-12-15 21:11 ` Glauber Costa
2011-12-15 22:44 ` David Miller
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=1323941672-14324-1-git-send-email-glommer@parallels.com \
--to=glommer@parallels.com \
--cc=cgroups@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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
all inboxes | Powered by JetHome®