[pve-devel] pve-manager and disk IO monitoring

[Alexandre DERUMIER]

>>@Alexandre: This was for performance reasons?

yes, I think. (don't remember exactly).
see the original post from stefan

http://pve.proxmox.com/pipermail/pve-devel/2012-August/003347.html

"Hello list,

right now when you select SCSI proxmox always use scsi-hd for device. 
With virtio-scsi-pci as scsihw we can also select scsi-block or 
scsi-generic.

With scsi-block and scsi-generic you can bypass qemu scsi emulation and 
use trim / discard support as the guest can talk directly to the 
underlying storage.

Also scsi-generic (needs guest kernel 3.4) is a lot faster then scsi-hd 
or scsi-block.

What would be the expected way to integrate a selection between them in 
proxmox?

"



----- Mail original -----
De: "dietmar" <dietmar at proxmox.com>
À: "datanom.net" <mir at datanom.net>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 30 Septembre 2016 07:50:11
Objet: Re: [pve-devel] pve-manager and disk IO monitoring

> So my question is: Why use scsi-generic instead of scsi-block when 
> scsi-generic prevents blockstats? 

commit d454d040338a6216c8d3e5cc9623d6223476cb5a 
Author: Alexandre Derumier <aderumier at odiso.com> 
Date: Tue Aug 28 12:46:07 2012 +0200 

use scsi-generic by default with libiscsi 

This add scsi passthrough with libiscsi 

Signed-off-by: Alexandre Derumier <aderumier at odiso.com> 


@Alexandre: This was for performance reasons? 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel