mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Octavian Purdila <opurdila@ixiacom.com>
To: Cong Wang <amwang@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Eric Dumazet <eric.dumazet@gmail.com>,
	linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	Neil Horman <nhorman@tuxdriver.com>,
	linux-sctp@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [RFC Patch] net: reserve ports for applications using fixed port numbers
Date: Thu, 4 Feb 2010 14:44:01 +0200	[thread overview]
Message-ID: <201002041444.01897.opurdila@ixiacom.com> (raw)
In-Reply-To: <4B6A3DBA.1000706@redhat.com>

On Thursday 04 February 2010 05:23:38 you wrote:

> > I think it might be useful to allow setting individual ports as reserved,
> > not only ranges, for example by using a bitmap.
> 
> This is a good idea, but I am not sure if this will be overkill? :-/
> Also, using bitmap is not friendly to sysctl interface, I am afraid.
> 

My concern is that we can have multiple applications that require a fixed port 
and if those ports are significantly apart we will decrease the port range 
available for connect. And that will hurt the rate of which new connections 
can be opened.

As for the sysctl interface I agree, I don't think it is even possible to  
cleanly use a bitmap through sysctl.

The options I see are either enhance sysctl to support bitmaps or use a 
dedicated /proc/net entry. 

I want to give this a try, which one do you people think is better?

  reply	other threads:[~2010-02-04 12:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03  4:30 Amerigo Wang
2010-02-03  4:39 ` Eric Dumazet
2010-02-03  5:15   ` Cong Wang
2010-02-03 11:12 ` Octavian Purdila
2010-02-04  3:23   ` Cong Wang
2010-02-04 12:44     ` Octavian Purdila [this message]
2010-02-04 17:41       ` David Miller
2010-02-04 18:15         ` Octavian Purdila
2010-02-04 18:21           ` David Miller
2010-02-04 21:45           ` Tetsuo Handa
2010-02-04 21:56             ` David Miller
2010-02-05  0:41               ` Tetsuo Handa
2010-02-05  1:05                 ` Octavian Purdila
2010-02-05  6:01                   ` Cong Wang
2010-02-05 12:28                     ` Octavian Purdila
2010-02-05  4:45           ` Cong Wang
2010-02-05 12:05             ` Octavian Purdila
2010-02-08  3:21               ` Cong Wang
2010-02-08 16:51                 ` Octavian Purdila
2010-02-05  7:11 ` Bart Van Assche
2010-02-05  7:25   ` Cong Wang
2010-02-05  9:08     ` [RFC Patch] net: reserve ports for applications using fixed portnumbers Tetsuo Handa

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=201002041444.01897.opurdila@ixiacom.com \
    --to=opurdila@ixiacom.com \
    --cc=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    /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

Powered by JetHome