netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Ben Greear <greearb@candelatech.com>
Cc: anton@samba.org, netdev@oss.sgi.com
Subject: Re: 100 network limit
Date: Fri, 29 Aug 2003 02:03:41 +0200	[thread overview]
Message-ID: <20030829020341.706356e7.ak@suse.de> (raw)
In-Reply-To: <3F4E783F.6080707@candelatech.com>

On Thu, 28 Aug 2003 14:46:39 -0700
Ben Greear <greearb@candelatech.com> wrote:

> 
> Since you can rename devices, that might not work. 

When someone renames eth1 to eth2 and the bitmap  doesn't have eth2 set and selects it 
then you can just retry, searching for further free bits.

When someone renames eth2 to eth1 the rename code should just clear the bit
of eth2 before the rename.

-Andi

      parent reply	other threads:[~2003-08-29  0:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 18:00 100 network limit Anton Blanchard
2003-08-28 19:08 ` Andi Kleen
2003-08-28 21:46   ` Ben Greear
2003-08-28 23:41     ` David S. Miller
2003-08-29  3:45       ` Ben Greear
2003-08-29  0:03     ` Andi Kleen [this message]

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=20030829020341.706356e7.ak@suse.de \
    --to=ak@suse.de \
    --cc=anton@samba.org \
    --cc=greearb@candelatech.com \
    --cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).