mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: glommer@parallels.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	cgroups@vger.kernel.org, kamezawa.hiroyu@jp.fujitsu.com,
	eric.dumazet@gmail.com, sfr@canb.auug.org.au
Subject: Re: [PATCH 2/2] Explicitly call tcp creation and init from memcontrol.c
Date: Thu, 15 Dec 2011 17:44:11 -0500 (EST)	[thread overview]
Message-ID: <20111215.174411.213210944798851570.davem@davemloft.net> (raw)
In-Reply-To: <4EEA6288.1080405@parallels.com>

From: Glauber Costa <glommer@parallels.com>
Date: Fri, 16 Dec 2011 01:11:36 +0400

> How about the following patch then ? I am keeping protocols that has
> the cgroup stuff on in a separate list, that can be protected by a
> mutex. Therefore we can allocate without going into troubles.

This is a significantly better approach, please test and submit this
patch formally.

Thanks.

      reply	other threads:[~2011-12-15 22:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  9:34 [PATCH 0/2] Proposed fixes for tcp memory pressure Glauber Costa
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 [this message]

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=20111215.174411.213210944798851570.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cgroups@vger.kernel.org \
    --cc=eric.dumazet@gmail.com \
    --cc=glommer@parallels.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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®