About thread_local and TmapMigratePP.DataScan case

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

 



Hi all,

anyone who knows what's the special thing with TmapMigratePP.DataScan
case. When I introduce thread_local variable in
PR(https://github.com/ceph/ceph/pull/9783/files#diff-254a8401d238ec25c714a5596f85b5ebL64),
it always failed because the thread local variable is assigned to zero
when execute this test!

For example, when tid == 512596224 local_center should be 5fed4e48,
but after begin this test case, this thread_local variable is assigned
to zero!:
tid=-512596224 local_center=5fed4e48 this=5fed4e48
[New Thread 0x7fffdef21700 (LWP 11835)]
tid=-512596224 local_center=5fed4e48 this=5fed4e48
[New Thread 0x7fffde720700 (LWP 11836)]
[New Thread 0x7fffddf1f700 (LWP 11837)]
[New Thread 0x7fffdd71e700 (LWP 11838)]
[New Thread 0x7fffdcf1d700 (LWP 11839)]
[New Thread 0x7fffdc71c700 (LWP 11840)]
[New Thread 0x7fffdbf1b700 (LWP 11841)]
tid=-134366272 local_center=0 this=5fed4e48
tid=-134366272 local_center=0 this=5fed4e48
tid=-134366272 local_center=0 this=5fed4e48
tid=-512596224 local_center=0 this=5fed4e48


QA job:http://qa-proxy.ceph.com/teuthology/haomai-2016-06-27_03:55:04-rados-wip-haomai-testing---basic-smithi/279412/teuthology.log

This can be repeated locally and I want to know what's the difference
this case introduced
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux