From: "Jan Beulich" <JBeulich@novell.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH linux-2.6.18-xen] blktap: make max # of tap devices a module parameter
Date: Tue, 22 Feb 2011 15:49:28 +0000 [thread overview]
Message-ID: <4D63E918020000780003327C@vpn.id2.novell.com> (raw)
In-Reply-To: <4D63C644.1000503@redhat.com>
>>> On 22.02.11 at 15:20, Laszlo Ersek <lersek@redhat.com> wrote:
> Hi,
>
> should anybody still use the blktap(1) driver in linux-2.6.18-xen, the
> following patch intends to make the maximum number of tapdevs
> configurable at module insertion time. The number is clamped to [256 ..
> NR_EVENT_CHANNELS]. I removed the definition of MAX_DEV_NAME because it
> didn't seem to be used at all.
>
> Thanks for considering,
> Laszlo Ersek
Without replacing the call to register_chrdev() with one to
__register_chrdev() (available only with 2.6.32 and newer) I
can't see how you would get beyond 256 devices with the
changes you propose.
Jan
next prev parent reply other threads:[~2011-02-22 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 14:20 [PATCH linux-2.6.18-xen] blktap: make max # of tap devices a module parameter Laszlo Ersek
2011-02-22 15:49 ` Jan Beulich [this message]
2011-02-22 17:34 ` Laszlo Ersek
2011-02-22 17:44 ` Daniel Stodden
2011-02-22 18:08 ` Laszlo Ersek
2011-02-22 18:59 ` Daniel Stodden
2011-02-23 10:38 ` Jan Beulich
2011-02-24 16:40 ` Jan Beulich
2011-02-24 19:59 ` Daniel Stodden
2011-02-24 20:10 ` Daniel Stodden
2011-02-23 9:42 ` Jan Beulich
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=4D63E918020000780003327C@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=lersek@redhat.com \
--cc=xen-devel@lists.xensource.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).