All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Hunt <johunt@akamai.com>
To: netfilter-devel@vger.kernel.org
Subject: ipset restore behavior with newer glibc
Date: Wed, 31 Oct 2012 11:27:12 -0500	[thread overview]
Message-ID: <50915160.1090908@akamai.com> (raw)

When doing an ipset restore with newer versions of glibc I'm seeing some 
extra syscall overhead that I was not seeing with glibc 2.4. I was 
wondering if anyone has seen such behavior and could help me understand 
what is going on?

Here is a snippet of strace during the restore with glibc 2.4: 
http://pastebin.com/qxkPF7FB and one with glibc 2.7: 
http://pastebin.com/wga9SN0E
I've also seen similar behavior with glibc 2.11.

You'll notice that with the newer version a second netlink socket is 
created and it appears some data is sent and info received back from the 
kernel and that socket is closed. This creating and closing of sockets 
continues until the restore operation completes. This causes the restore 
to grow from taking ~1 second to ~5 seconds. This is not a huge deal, 
but I'm more curious as to why this behavior has changed.

These runs were done with ipset v6.11 and kernel 3.2. It appears to me 
this is a glibc change b/c if I swap out only that component I see this 
change in behavior.

Thanks
Josh

             reply	other threads:[~2012-10-31 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 16:27 Josh Hunt [this message]
2012-10-31 16:41 ` ipset restore behavior with newer glibc Jan Engelhardt
2012-10-31 18:49   ` Jozsef Kadlecsik
2012-10-31 19:07     ` Jozsef Kadlecsik
2012-11-27 19:18       ` Josh Hunt
2012-11-27 19:51         ` Jozsef Kadlecsik
2012-11-27 19:53           ` Josh Hunt
2012-10-31 19:30     ` Josh Hunt

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=50915160.1090908@akamai.com \
    --to=johunt@akamai.com \
    --cc=netfilter-devel@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 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.