On Wed, Aug 29, 2012 at 8:17 AM, Bo Yang wrote:
> On 08/29/2012 02:45 PM, Stefan Hajnoczi wrote:
>> BTW, guest driver out-of-memory is not the hardware's problem. The
>> driver needs to handle it. For example, the Linux e100 driver has a
>> watchdog timer which will raise an interrupt to refill
On 08/29/2012 02:45 PM, Stefan Hajnoczi wrote:
> On Wed, Aug 29, 2012 at 1:55 AM, Bo Yang wrote:
>> On 08/28/2012 06:59 PM, Stefan Hajnoczi wrote:
>>> On Tue, Aug 28, 2012 at 7:23 AM, Bo Yang wrote:
According
to liunux driver's implementation, the descriptor with EL bit set
must no
On Wed, Aug 29, 2012 at 1:55 AM, Bo Yang wrote:
> On 08/28/2012 06:59 PM, Stefan Hajnoczi wrote:
>> On Tue, Aug 28, 2012 at 7:23 AM, Bo Yang wrote:
>>> According
>>> to liunux driver's implementation, the descriptor with EL bit set
>>> must not be touched by hardware, usually, the buffer size of
On 08/28/2012 06:59 PM, Stefan Hajnoczi wrote:
> On Tue, Aug 28, 2012 at 7:23 AM, Bo Yang wrote:
>> According
>> to liunux driver's implementation, the descriptor with EL bit set
>> must not be touched by hardware, usually, the buffer size of this
>> descriptor is set to 0.
>
> Please describe th
On Tue, Aug 28, 2012 at 7:23 AM, Bo Yang wrote:
> According
> to liunux driver's implementation, the descriptor with EL bit set
> must not be touched by hardware, usually, the buffer size of this
> descriptor is set to 0.
Please describe the bug you are seeing and how to reproduce it. It's
not c
The guest may enter into state of no receive descriptors,
and if there is no interrupt, the descriptor filling function
has no chance to run again,which causes network stall. According
to liunux driver's implementation, the descriptor with EL bit set
must not be touched by hardware, usually, the bu
