From: andrew may <acmay@acmay.homeip.net>
To: linux-kernel@vger.kernel.org
Subject: What is the best way for multiple net_devices
Date: Wed, 27 Jun 2001 14:52:01 -0700 [thread overview]
Message-ID: <20010627145201.A23834@ecam.san.rr.com> (raw)
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
It seems to me that this will waste space creating copies of all the
static data.
Then there are things like ipsec that create a few static net_dev
structures, but I have no idea how they deal with more entries.
They probably don't.
The PCI drivers seem to be pretty clean with init_one type functions.
Is there anything similar for generic hardware-less network devices.
I would hate to have write an ioctl to create a new device without
loading a module twice.
--
Andrew May
acmay@acmay.homeip.net
next reply other threads:[~2001-06-27 21:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 21:52 andrew may [this message]
2001-06-27 22:04 ` What is the best way for multiple net_devices Jeff Garzik
2001-06-27 22:18 ` andrew may
2001-06-27 22:36 ` Maksim Krasnyanskiy
2001-06-27 23:16 ` andrew may
[not found] <993679536.14418@whiskey.enposte.net>
2001-06-27 22:19 ` Stuart Lynne
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 12:35 Jesse Pollard
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=20010627145201.A23834@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=linux-kernel@vger.kernel.org \
/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