I think you need a release memory barrier if you store into a hazard
pointer that is non null to prevent prior accesses from occurring after
the store. That's an extra memory barrier for hazard pointers that I
overlooked. One thing that could be done is wait an extra RCU grace
period after the hazard pointer scan to ensure prior accesses have
completed before freeing the resource. That would lengthen the delay
to approximately 2 RCU grace periods. Could be a problem if you have
a high write rate and are trying to keep that delay minimal.
There might be another way. I'd have to investigate it a little more.
--
Joe Seigh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
