From: David Vrabel <david.vrabel@citrix.com>
To: byungchul.so@samsung.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Question about xen event channel
Date: Mon, 11 Jul 2016 10:26:11 +0100 [thread overview]
Message-ID: <57836633.3090305@citrix.com> (raw)
In-Reply-To: <20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4>
On 11/07/16 04:58, 소병철 wrote:
> Hello everyone :)
>
>
>
> I have a question about xen event channel. Is it possible to allocate
> two event channels in one xen frontend driver?
Yes. For example, netif can have a separate Tx and Rx event channel.
David
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-11 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4>
2016-07-11 3:58 ` Question about xen event channel 소병철
2016-07-11 9:26 ` David Vrabel [this message]
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=57836633.3090305@citrix.com \
--to=david.vrabel@citrix.com \
--cc=byungchul.so@samsung.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 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).