On 04/20/2017 03:05 PM, Jan Kiszka wrote:
On 2017-04-20 08:51, Wei Wang wrote:
On 04/19/2017 10:52 PM, Jan Kiszka wrote:
On 2017-04-19 16:33, Wang, Wei W wrote:
On 04/19/2017 07:21 PM, Jan Kiszka wrote:
On 2017-04-19 13:11, Wei Wang wrote:
On 04/19/2017 06:36 PM, Jan Kiszka wrote:
On 2017-0
On 2017-04-20 08:51, Wei Wang wrote:
> On 04/19/2017 10:52 PM, Jan Kiszka wrote:
>> On 2017-04-19 16:33, Wang, Wei W wrote:
>>> On 04/19/2017 07:21 PM, Jan Kiszka wrote:
On 2017-04-19 13:11, Wei Wang wrote:
> On 04/19/2017 06:36 PM, Jan Kiszka wrote:
>> On 2017-04-19 12:02, Wei Wang wr
On 04/19/2017 10:52 PM, Jan Kiszka wrote:
On 2017-04-19 16:33, Wang, Wei W wrote:
On 04/19/2017 07:21 PM, Jan Kiszka wrote:
On 2017-04-19 13:11, Wei Wang wrote:
On 04/19/2017 06:36 PM, Jan Kiszka wrote:
On 2017-04-19 12:02, Wei Wang wrote:
The design presented here intends to use only one BA
On 2017-04-19 16:33, Wang, Wei W wrote:
> On 04/19/2017 07:21 PM, Jan Kiszka wrote:
>> On 2017-04-19 13:11, Wei Wang wrote:
>>> On 04/19/2017 06:36 PM, Jan Kiszka wrote:
On 2017-04-19 12:02, Wei Wang wrote:
> The design presented here intends to use only one BAR to expose
> bot
On 04/19/2017 07:21 PM, Jan Kiszka wrote:
> On 2017-04-19 13:11, Wei Wang wrote:
> > On 04/19/2017 06:36 PM, Jan Kiszka wrote:
> >> On 2017-04-19 12:02, Wei Wang wrote:
> >>> The design presented here intends to use only one BAR to expose
> >>> both TX and RX. The two VMs share an intermedi
On 2017-04-19 13:11, Wei Wang wrote:
> On 04/19/2017 06:36 PM, Jan Kiszka wrote:
>> On 2017-04-19 12:02, Wei Wang wrote:
>>> The design presented here intends to use only one BAR to expose
>>> both TX and RX. The two VMs share an intermediate memory
>>> here, why couldn't we give the sa
On 04/19/2017 06:36 PM, Jan Kiszka wrote:
On 2017-04-19 12:02, Wei Wang wrote:
The design presented here intends to use only one BAR to expose
both TX and RX. The two VMs share an intermediate memory
here, why couldn't we give the same permission to TX and RX?
For security and/or safety reason
On 2017-04-19 12:02, Wei Wang wrote:
> The design presented here intends to use only one BAR to expose
> both TX and RX. The two VMs share an intermediate memory
> here, why couldn't we give the same permission to TX and RX?
>
For security and/or safety reasons: the TX side can
On 04/19/2017 05:31 PM, Jan Kiszka wrote:
On 2017-04-19 11:09, Wei Wang wrote:
On 04/19/2017 04:49 PM, Jan Kiszka wrote:
On 2017-04-19 10:42, Wei Wang wrote:
On 04/19/2017 03:35 PM, Jan Kiszka wrote:
On 2017-04-19 08:38, Wang, Wei W wrote:
Hi,
We made some design changes to the original
On 2017-04-19 11:09, Wei Wang wrote:
> On 04/19/2017 04:49 PM, Jan Kiszka wrote:
>> On 2017-04-19 10:42, Wei Wang wrote:
>>> On 04/19/2017 03:35 PM, Jan Kiszka wrote:
On 2017-04-19 08:38, Wang, Wei W wrote:
> Hi,
>We made some design changes to the original vhost-pci design,
>
On 04/19/2017 04:49 PM, Jan Kiszka wrote:
On 2017-04-19 10:42, Wei Wang wrote:
On 04/19/2017 03:35 PM, Jan Kiszka wrote:
On 2017-04-19 08:38, Wang, Wei W wrote:
Hi,
We made some design changes to the original vhost-pci design, and want
to open
a discussion about the latest design (labelled
On 2017-04-19 10:42, Wei Wang wrote:
> On 04/19/2017 03:35 PM, Jan Kiszka wrote:
>> On 2017-04-19 08:38, Wang, Wei W wrote:
>>> Hi,
>>> We made some design changes to the original vhost-pci design, and want
>>> to open
>>> a discussion about the latest design (labelled 2.0) and its extension
>>>
12 matches
Mail list logo
