From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org, netdev@vger.kernel.org,
david.vrabel@citrix.com, ian.campbell@citrix.com
Subject: Re: [Xen-devel] [PATCH net-next V2 1/2] xen-netback: split event channels support for Xen backend driver
Date: Wed, 22 May 2013 11:17:54 -0400 [thread overview]
Message-ID: <20130522151754.GD8162@phenom.dumpdata.com> (raw)
In-Reply-To: <1369161310-9529-2-git-send-email-wei.liu2@citrix.com>
> +/* Provide an option to disable split event channels at load time as
> + * event channels are limited resource. Split event channels are
> + * enabled by default.
> + */
> +unsigned int feature_split_event_channels = 1;
> +module_param(feature_split_event_channels, uint, 0644);
How about just 'seperate_tx_rx_irq' ? Much easier to comprehend I think?
next prev parent reply other threads:[~2013-05-22 15:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 18:35 [PATCH net-next 0/2 V2] Xen network: split event channels support Wei Liu
2013-05-21 18:35 ` [PATCH net-next V2 1/2] xen-netback: split event channels support for Xen backend driver Wei Liu
2013-05-21 18:35 ` Wei Liu
2013-05-22 8:05 ` [Xen-devel] " Jan Beulich
2013-05-22 8:05 ` Jan Beulich
2013-05-22 15:17 ` Konrad Rzeszutek Wilk
2013-05-22 15:17 ` Konrad Rzeszutek Wilk [this message]
2013-05-22 15:35 ` Wei Liu
2013-05-22 15:35 ` [Xen-devel] " Wei Liu
2013-05-22 15:40 ` annie li
2013-05-22 15:40 ` annie li
2013-05-22 15:50 ` Wei Liu
2013-05-22 15:50 ` Wei Liu
2013-05-21 18:35 ` [PATCH net-next V2 2/2] xen-netfront: split event channels support for Xen frontend driver Wei Liu
2013-05-22 8:13 ` [Xen-devel] " Jan Beulich
2013-05-22 8:13 ` Jan Beulich
2013-05-21 18:35 ` Wei Liu
2013-05-22 8:35 ` [PATCH net-next 0/2 V2] Xen network: split event channels support Ian Campbell
2013-05-22 8:35 ` Ian Campbell
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=20130522151754.GD8162@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.