All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	Nikolay Aleksandrov <nikolay@redhat.com>
Subject: Re: getaddrinfo slowdown in 3.17.1, due to getifaddrs
Date: Tue, 21 Oct 2014 15:25:57 +0200	[thread overview]
Message-ID: <20141021132557.GA9440@sesse.net> (raw)
In-Reply-To: <20141017062517.GA11584@casper.infradead.org>

On Fri, Oct 17, 2014 at 07:25:17AM +0100, Thomas Graf wrote:
> I think the only option at this point is to re-add the nltable lock to
> netlink_lookup() so we can drop the synchronize_net() until we find a
> way to RCUify socket destruction. I will cook up a patch today unless
> somebody can come up with a smarter way to work around needing the
> synchronize_net().

Did you end up with a patch? We'd like to reboot the server in question
soon-ish, but it's an open question whether we should go to 3.16.x, revert
exactly the patches in question or something else.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

  parent reply	other threads:[~2014-10-21 13:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17  0:21 getaddrinfo slowdown in 3.17.1, due to getifaddrs Steinar H. Gunderson
2014-10-17  0:34 ` Steinar H. Gunderson
2014-10-17  6:25   ` Thomas Graf
2014-10-17 16:28     ` Eric Dumazet
2014-10-17 16:30       ` David Miller
2014-10-17 21:19         ` Eric Dumazet
2014-10-21 13:25     ` Steinar H. Gunderson [this message]
2014-10-21 13:31       ` Thomas Graf
2014-10-23 23:37         ` Steinar H. Gunderson
2014-11-02 21:55           ` Steinar H. Gunderson
2014-11-02 23:25             ` David Miller
2014-10-18 10:45   ` Steinar H. Gunderson

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=20141021132557.GA9440@sesse.net \
    --to=sgunderson@bigfoot.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nikolay@redhat.com \
    --cc=tgraf@suug.ch \
    /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.