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

RE: [Xen-devel] [PATCH 1/3] Output Virtual Block Device requests information to /proc/xen/vbd

  • To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Satoshi Uchida" <s-uchida@xxxxxxxxxxxxx>
  • Date: Thu, 22 Jun 2006 18:17:10 +0900
  • Delivery-date: Thu, 22 Jun 2006 02:17:36 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcaVTZ+kPkNsRuw/QCaj3wrQUPbQqQASMB1QABGGNvA=


> I looked at the code, and it seems "oo" stands of "out of", which  
> indicates how much we were out of request (Xen supports up to 64 
> requests in queue)

It may be correct.

>Few minor comments:
>- The variable dom_io_info_wq is unused, should be removed.
>- printk("%s: out of memory\n", __FUNCTION__) should be used with 

I want to review around these codes.

>I have one question: in your below output:
>> Domain 4 - oo        0  rd    18699  wr        2
>>  xvd 4  8:21 - oo        0  rd    18699  wr        2
>I notice that you output the domid with xvd (4), but in the above line, we 
>already had that information (Domain 4).
> So why you need to show the domid again?

VBD processes in domain0 runs as xvd threads.
These threads names "xvd [Domain name] [Major Number]:[Minor Number]".
So, I show same name inelligibly.
In addition, I think that total Information for each domain is added optionally.
Therefore, its informatin is needed in such time.

Satoshi UCHIDA

Xen-devel mailing list



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