public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sl@whiskey.fireplug.net (Stuart Lynne)
To: linux-kernel@vger.kernel.org
Subject: Re: What is the best way for multiple net_devices
Date: 27 Jun 2001 15:19:39 -0700	[thread overview]
Message-ID: <9hdm5r$e9i$1@whiskey.enposte.net> (raw)
In-Reply-To: <993679536.14418@whiskey.enposte.net>

In article <993679536.14418@whiskey.enposte.net>,
Jeff Garzik <jgarzik@mandrakesoft.com> wrote:
>andrew may wrote:
>> 
>> Is there a standard way to make multiple copies of a network device?
>> 
>> For things like the bonding/ipip/ip_gre and others they seem to expect
>> insmod -o copy1 module.o
>> insmod -o copy2 module.o
>
>The network driver should provide the capability to add new devices.
>
>Most drivers currently have the capability to do N devices, where N is
>some constant set at compile time.  Typically you use ifconfig, a
>special-purpose userland program, or sometimes even sysctls to configure
>additional net devices.

Ioctls require modifications to other parts of the kernel and a supporting
user land program.

Passing the number to create via insmod seems to be a reasonable compromise.

>It's certainly possible to modify the driver to create additional
>network interfaces on the fly, but a lot of drivers are not coded to do
>that at present.

-- 
                                            __O 
Lineo - For Embedded Linux Solutions      _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net>       www.fireplug.net        604-461-7532

       reply	other threads:[~2001-06-27 22:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <993679536.14418@whiskey.enposte.net>
2001-06-27 22:19 ` Stuart Lynne [this message]
2001-06-28 12:35 What is the best way for multiple net_devices Jesse Pollard
  -- strict thread matches above, loose matches on Subject: below --
2001-06-27 21:52 andrew may
2001-06-27 22:04 ` Jeff Garzik
2001-06-27 22:18   ` andrew may
2001-06-27 22:36   ` Maksim Krasnyanskiy
2001-06-27 23:16     ` andrew may

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='9hdm5r$e9i$1@whiskey.enposte.net' \
    --to=sl@whiskey.fireplug.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sl@fireplug.net \
    /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