* Question about xen event channel [not found] <CGME20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4> @ 2016-07-11 3:58 ` 소병철 2016-07-11 9:26 ` David Vrabel 0 siblings, 1 reply; 2+ messages in thread From: 소병철 @ 2016-07-11 3:58 UTC (permalink / raw) To: xen-devel [-- Attachment #1.1: Type: text/html, Size: 3833 bytes --] [-- Attachment #1.2: 201602111742151_N3WZA6X7.png --] [-- Type: image/png, Size: 33527 bytes --] [-- Attachment #2: Type: text/plain, Size: 127 bytes --] _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Question about xen event channel 2016-07-11 3:58 ` Question about xen event channel 소병철 @ 2016-07-11 9:26 ` David Vrabel 0 siblings, 0 replies; 2+ messages in thread From: David Vrabel @ 2016-07-11 9:26 UTC (permalink / raw) To: byungchul.so, xen-devel 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
![[-- Attachment #1.2: 201602111742151_N3WZA6X7.png --] [-- Type: image/png, Size: 33527 bytes --]](../../20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4/1.2-201602111742151_N3WZA6X7.png){kind=link}
end of thread, other threads:[~2016-07-11 9:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CGME20160711035849epcms1p41368d9cffd9272e62f6f8ccc03d98ea0@epcms1p4>
2016-07-11 3:58 ` Question about xen event channel 소병철
2016-07-11 9:26 ` David Vrabel
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).