From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: davem@redhat.com, rick@rlknight.com
Subject: Re: Dummy network device
Date: Tue, 9 Mar 2004 21:22:21 -0800 [thread overview]
Message-ID: <20040309212221.766479dc.rddunlap@osdl.org> (raw)
In-Reply-To: <20040309162552.0d7f1ca0.rddunlap@osdl.org>
| From: Rick Knight
|
| David S. Miller wrote:
|
| >On Tue, 09 Mar 2004 15:11:48 -0800
| >Rick Knight <rick@rlknight.com> wrote:
| >
| >
| >
| >>I found the answer. From the archive. Decided to look at dummy.c and
| >>numdummies=1, changed it to numdummies=3 and rebuilt that module. Works
| >>like a charm.
| >>
| >>Question/Suggestion, couldn't this be made an option at configuration?
| >>Kind of like number_of_ptys=256.
| >>
| >>
| >
| >Specify "numdummies=3" on the module load command line.
| >
| >
| >It's supposed to be changeable at module load time, without
| >rebuilding it. Try this e.g.:
| >
| >modprobe dummy numdummies=4
| >
| >--
| >~Randy
| >
| >
| Randy, David,
|
| Thanks for the replies.
|
| I did try 'modprobe dummy numdummies=3', however, I didn't quote
| numdummies=3. Are the quote required? Is there a modprobe.conf option?
| Probably "options dummy "numdummies=3".
No, the quotes are not required. This works for me:
modprobe dummy numdummies=3
Using /etc/modprobe.conf also works, as you suggested, but without
the quotation marks:
options dummy numdummies=3
Either way shows this in /proc/net/dev:
dummy0: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
dummy1: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
dummy2: 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0
HTH.
--
~Randy
next parent reply other threads:[~2004-03-10 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040309162552.0d7f1ca0.rddunlap@osdl.org>
2004-03-10 5:22 ` Randy.Dunlap [this message]
2004-03-10 16:53 ` Rick Knight
2004-03-09 23:11 Rick Knight
2004-03-09 23:18 ` Randy.Dunlap
2004-03-09 23:21 ` David S. Miller
2004-03-09 23:37 ` Rick Knight
-- strict thread matches above, loose matches on Subject: below --
2004-03-09 22:02 Richard W. Knight
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=20040309212221.766479dc.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rick@rlknight.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
all inboxes | Powered by JetHome®