From: Octavian Purdila <opurdila@ixiacom•com>
To: netdev@vger•kernel.org
Subject: [net-next PATCH v3 0/3] net: reserve ports for applications using fixed port numbers
Date: Thu, 11 Feb 2010 04:55:33 +0200 [thread overview]
Message-ID: <201002110455.33545.opurdila@ixiacom.com> (raw)
(Resending to netdev since I've misspelled the email address. Apologies if you receive multiple copies)
This patch series is based on Amerigo's v2 but it now uses a bitmap
for port reservation.
I've ran a while (1) { bind(0) } test (with ip_local_port_range
1024 65000) to see if there is any performance difference between the
two approaches (ranges vs bitmap). I could not detect any significant
difference, both cases scored in 2.76s +/- 0.01 on my setup.
I've based this patch series on current net-next, but it contains a
significant non networking part. Please let me know if I should handle
this differently.
Octavian Purdila (3):
sysctl: refactor integer handling proc code
sysctl: add proc_dobitmap
net: reserve ports for applications using fixed port numbers
Documentation/networking/ip-sysctl.txt | 12 +
drivers/infiniband/core/cma.c | 7 +-
include/linux/sysctl.h | 2 +
include/net/ip.h | 6 +
kernel/sysctl.c | 374 +++++++++++++++++++-------------
net/ipv4/inet_connection_sock.c | 5 +
net/ipv4/inet_hashtables.c | 2 +
net/ipv4/sysctl_net_ipv4.c | 7 +
net/ipv4/udp.c | 3 +-
net/sctp/socket.c | 2 +
10 files changed, 264 insertions(+), 156 deletions(-)
next reply other threads:[~2010-02-11 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 2:55 Octavian Purdila [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-11 2:09 [net-next PATCH v3 0/3] net: reserve ports for applications using fixed port numbers Octavian Purdila
2010-02-15 12:36 ` Cong Wang
2010-02-15 12:39 ` Cong Wang
2010-02-15 12:37 ` Octavian Purdila
2010-02-15 12:48 ` Cong Wang
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=201002110455.33545.opurdila@ixiacom.com \
--to=opurdila@ixiacom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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