From mboxrd@z Thu Jan 1 00:00:00 1970 From: Octavian Purdila Subject: Re: [net-next PATCH v4 0/3] net: reserve ports for applications using fixed port Date: Tue, 16 Feb 2010 21:51:04 +0200 Message-ID: <201002162151.04861.opurdila@ixiacom.com> References: <1266271241-6293-1-git-send-email-opurdila@ixiacom.com> <201002162004.33533.opurdila@ixiacom.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: David Miller , Linux Kernel Network Developers , Linux Kernel Developers , Amerigo Wang To: "Eric W. Biederman" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tuesday 16 February 2010 20:49:37 you wrote: > > The use case (large bitmaps/lists) is different enough from what we have > > today (small bitmaps) and that is why I think that we need this new > > interface. > > > > If I get bitmap_parse_user correctly, for a 64k bitmap it expects a 2K > > comma separated values. That is not the most intuitively way for the > > user to set a list of ports he wants to reserve. > > In this case I expect an interface of comma separated ranges would be > ideal. Typically compact, and modifiable by writing the new value to > the file. > Something like bellow? # set bits 8080 and 1666 $echo 8080 1666-1666 > /proc #reset bit 1666 $echo 8080 > /proc #reset whole bitmap $echo > /proc > I think the default value would be something like 32768-61000. Note that this new proc entry will work in conjunction with the existing ip_local_port_range option, so the default bitmap can (and should be) empty.