[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] FE driver and log dirty


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Mon, 14 Jul 2008 08:27:45 +0100
  • Cc:
  • Delivery-date: Mon, 14 Jul 2008 00:27:48 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcjlgcleH6AfAfjWTPSrkcaRDBcgVgAAVJuk
  • Thread-topic: [Xen-devel] FE driver and log dirty

On 14/7/08 08:18, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> **There must be some CPU issued accesses to target data page
> before xen_suspend is invoked, if that page is serviced by BE driver
> and has been dequeued from FE queues within the loop copy
> process. Or else log dirty mode is not triggered to re-transimit that
> page in next loop. **
> 
> Does that assumption always hold true for existing FE drivers?

Not sure what you mean? There can be requests which the FE re-queues after
resume which have in fact already been satisfied (pre-suspend) and even the
response queued up in the old shared request/response ring. The key is that
replaying them is idempotent.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.