[pve-devel] [PATCH 2/2] monitor diskio with qmp command

[Dietmar Maurer]

I just uploaded some experimental code to the git repository:

https://git.proxmox.com/?p=qemu-server.git;a=commit;h=30a3378acdd2a6c40998a455c26437888fd98196

This can completely replace the current code. What do you think?

(just set exec flag on the file, then you can start it and play around).

- Dietmar

> >>IMHO Perl Threads are nonsense. They do not share any data, so
> >>starting a new thread need to copy data and is slow. Basically, it
> >>combines the disadvantages of "multiple processes" and threads.
> 
> Ah ok, yes, copying datas for new thread is really a nonsense.
> 
> 
> I'm currently reading IO::Multiplex doc, i'm not sure to be enough good with
> perl to implement this ;)
> 
> 
> ----- Mail original -----
> 
> De: "Dietmar Maurer" <dietmar at proxmox.com>
> À: "Alexandre DERUMIER" <aderumier at odiso.com>
> Cc: pve-devel at pve.proxmox.com
> Envoyé: Mercredi 11 Juillet 2012 06:10:57
> Objet: RE: [pve-devel] [PATCH 2/2] monitor diskio with qmp command
> 
> > http://search.cpan.org/~nilsonsfj/subs-parallel-0.08/lib/subs/parallel
> > .pm
> > or
> > http://search.cpan.org/~odigity/Parallel-Simple-0.01/lib/Parallel/Simp
> > le.pm
> >
> > (But maybe they use some king of threads or fork ?)
> >
> > They is no way to do real threading with perl ?
> 
> IMHO Perl Threads are nonsense. They do not share any data, so starting a
> new thread need to copy data and is slow. Basically, it combines the
> disadvantages of "multiple processes" and threads.
> 
> But I tested that a long time ago, and do not know it that is now better.
> 
> - Dietmar
> 
> 
> 
> --
> 
> --
> 
> 
> 
> 
> 
> Alexandre D e rumier
> 
> Ingénieur Systèmes et Réseaux
> 
> 
> Fixe : 03 20 68 88 85
> 
> Fax : 03 20 68 90 88
> 
> 
> 45 Bvd du Général Leclerc 59100 Roubaix
> 12 rue Marivaux 75002 Paris