Re: [PATCH 4/6] kvm tools: Add rwlock wrapper

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

 



* Paul E. McKenney <paulmck@xxxxxxxxxxxxxxxxxx> wrote:

> And the other reason that you want to mark the readers is for debug 
> purposes.  Murphy being who he is, you will some day need to check 
> for someone calling the "OK to update" function while they are 
> acting as a reader.

Correct. In one of the previous mails i suggested a debug mode that 
switches it all to pthread rwlocks.

We do not want to lose the identify of what the read paths are: this 
could grow into a BKL-alike nasty-to-fix assumption over a couple of 
years! Then if someone finds a usecase that intensifies the frequency 
of one of the key writepaths, we'll be in trouble ...

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux