[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201002162151.04861.opurdila@ixiacom.com>
Date: Tue, 16 Feb 2010 21:51:04 +0200
From: Octavian Purdila <opurdila@...acom.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
Cc: David Miller <davem@...emloft.net>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Linux Kernel Developers <linux-kernel@...r.kernel.org>,
Amerigo Wang <amwang@...hat.com>
Subject: Re: [net-next PATCH v4 0/3] net: reserve ports for applications using fixed port
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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists