On Wed, Jul 18, 2012 at 9:21 PM, Bharata B Rao <bharata.rao@xxxxxxxxx> wrote:
On Wed, Jul 18, 2012 at 10:35 PM, Anand Avati <anand.avati@xxxxxxxxx> wrote:As you note below, I don't want to re-init but rather do fini and init :)
> Why do you want to re-init an already existing object?
My question came from a different angle. glfs_fini() will be destroying the entire object. You need to get hold of a new object with glfs_new() and do glfs_init() on the new object. I see no real reason in providing a glfs_fini() api which will result in partial destruction of glfs_t and also lets you to glfs_init() on it again. You might as well leave the glfs_t as-is and avoid an extra glfs_init() for the second access.
> Rather, why do youI agree, but the short answer is that for protocols like gluster where
> want to fini an object which you know you will init again? There is a cost
> to establishing and tearing down glfs_t. Why not initialize it once and use
> it for the lifetime of the process?
I am not required to specify any image format, QEMU ends up opening
the image twice which results in connection init and termination
twice.
As I said, why not just use a new glfs_t for the second access attempt?
Avati
