> On Apr 13, 2016, at 1:07 PM, John Snow wrote:
>
> Why do you want to use IDE? If you are looking for performance, why not
> a virtio device?
I’m just trying to understand how IDE emulation works and see where the
overhead comes in. Thank you for the detailed explanation. I really appreciate
On 04/13/2016 03:25 AM, Huaicheng Li (coperd) wrote:
>
>> On Mar 14, 2016, at 10:09 PM, Huaicheng Li wrote:
>>
>>
>>> On Mar 13, 2016, at 8:42 PM, Fam Zheng wrote:
>>>
>>> On Sun, 03/13 14:37, Huaicheng Li (coperd) wrote:
Hi all,
What I’m confused about is that:
If on
> On Mar 14, 2016, at 10:09 PM, Huaicheng Li wrote:
>
>
>> On Mar 13, 2016, at 8:42 PM, Fam Zheng wrote:
>>
>> On Sun, 03/13 14:37, Huaicheng Li (coperd) wrote:
>>> Hi all,
>>>
>>> What I’m confused about is that:
>>>
>>> If one I/O is too large and may need several rounds (say 2) of DMA
On Mon, Mar 14, 2016 at 10:09:17PM -0500, Huaicheng Li wrote:
>
> > On Mar 13, 2016, at 8:42 PM, Fam Zheng wrote:
> >
> > On Sun, 03/13 14:37, Huaicheng Li (coperd) wrote:
> >> Hi all,
> >>
> >> What I’m confused about is that:
> >>
> >> If one I/O is too large and may need several rounds (sa
> On Mar 13, 2016, at 8:42 PM, Fam Zheng wrote:
>
> On Sun, 03/13 14:37, Huaicheng Li (coperd) wrote:
>> Hi all,
>>
>> What I’m confused about is that:
>>
>> If one I/O is too large and may need several rounds (say 2) of DMA transfers,
>> it seems the second round transfer begins only after t
On Sun, Mar 13, 2016 at 02:37:21PM -0500, Huaicheng Li (coperd) wrote:
> I meet some trouble in understanding IDE emulation:
>
> (1) IDE I/O Down Path (In VCPU thread):
> upon KVM_EXIT_IO, corresponding disk ioport write function will write IO info
> to IDEState, then ide read callback function
On Sun, 03/13 14:37, Huaicheng Li (coperd) wrote:
> Hi all,
>
> What I’m confused about is that:
>
> If one I/O is too large and may need several rounds (say 2) of DMA transfers,
> it seems the second round transfer begins only after the completion of the
> first part, by reading data from **IDE
Hi all,
I meet some trouble in understanding IDE emulation:
(1) IDE I/O Down Path (In VCPU thread):
upon KVM_EXIT_IO, corresponding disk ioport write function will write IO info
to IDEState, then ide read callback function will eventually split it into
**several DMA transfers** and eventually
