我正在尝试在pthreads,semaphore.h和gcc atomic builtins之上实现一个由循环缓冲区支持的高性能阻塞队列。队列需要处理来自不同线程的多个同时读者和作者。
我已经隔离了某种竞争条件,我不确定它是否是关于某些原子操作和信号量行为的错误假设,或者我的设计是否存在根本缺陷。
我已将其提取并简化为以下独立示例。我希望这个程序永远不会回来。但是,在队列中检测到损坏的几十万次迭代之后它会返回。
在下面的示例中(用于说明),它实际上并不存储任何东西,它只是将一个单元格设置为1,该单元格将保存实际数据,而0表示一个空单元格。有一个计数信号量(空位)代表空置细胞的数量,另一个计数信号量(占用者)代表被占用细胞的数量。
作家执行以下操作:
读者反其道而行之:
我希望,鉴于上述情况,正好一个线程可以同时读取或写入任何给定的单元格。
关于它为什么不起作用或调试策略的任何想法都赞赏。下面的代码和输出......
#include <stdlib.h>
#include <semaphore.h>
#include <iostream>
using namespace std;
#define QUEUE_CAPACITY 8 // must be power of 2
#define NUM_THREADS 2
struct CountingSemaphore
{
sem_t m;
CountingSemaphore(unsigned int initial) { sem_init(&m, 0, initial); }
void post() { sem_post(&m); }
void wait() { sem_wait(&m); }
~CountingSemaphore() { sem_destroy(&m); }
};
struct BlockingQueue
{
unsigned int head; // (head % capacity) is next head position
unsigned int tail; // (tail % capacity) is next tail position
CountingSemaphore vacancies; // how many cells are vacant
CountingSemaphore occupants; // how many cells are occupied
int cell[QUEUE_CAPACITY];
// (cell[x] == 1) means occupied
// (cell[x] == 0) means vacant
BlockingQueue() :
head(0),
tail(0),
vacancies(QUEUE_CAPACITY),
occupants(0)
{
for (size_t i = 0; i < QUEUE_CAPACITY; i++)
cell[i] = 0;
}
// put an item in the queue
void put()
{
vacancies.wait();
// atomic post increment
set(__sync_fetch_and_add(&head, 1) % QUEUE_CAPACITY);
occupants.post();
}
// take an item from the queue
void take()
{
occupants.wait();
// atomic post increment
get(__sync_fetch_and_add(&tail, 1) % QUEUE_CAPACITY);
vacancies.post();
}
// set cell i
void set(unsigned int i)
{
// atomic compare and assign
if (!__sync_bool_compare_and_swap(&cell[i], 0, 1))
{
corrupt("set", i);
exit(-1);
}
}
// get cell i
void get(unsigned int i)
{
// atomic compare and assign
if (!__sync_bool_compare_and_swap(&cell[i], 1, 0))
{
corrupt("get", i);
exit(-1);
}
}
// corruption detected
void corrupt(const char* action, unsigned int i)
{
static CountingSemaphore sem(1);
sem.wait();
cerr << "corruption detected" << endl;
cerr << "action = " << action << endl;
cerr << "i = " << i << endl;
cerr << "head = " << head << endl;
cerr << "tail = " << tail << endl;
for (unsigned int j = 0; j < QUEUE_CAPACITY; j++)
cerr << "cell[" << j << "] = " << cell[j] << endl;
}
};
BlockingQueue q;
// keep posting to the queue forever
void* Source(void*)
{
while (true)
q.put();
return 0;
}
// keep taking from the queue forever
void* Sink(void*)
{
while (true)
q.take();
return 0;
}
int main()
{
pthread_t id;
// start some pthreads to run Source function
for (int i = 0; i < NUM_THREADS; i++)
if (pthread_create(&id, NULL, &Source, 0))
abort();
// start some pthreads to run Sink function
for (int i = 0; i < NUM_THREADS; i++)
if (pthread_create(&id, NULL, &Sink, 0))
abort();
while (true);
}
编译如下:
$ g++ -pthread AboveCode.cpp
$ ./a.out
每次输出都不同,但这里有一个例子:
corruption detected
action = get
i = 6
head = 122685
tail = 122685
cell[0] = 0
cell[1] = 0
cell[2] = 1
cell[3] = 0
cell[4] = 1
cell[5] = 0
cell[6] = 1
cell[7] = 1
我的系统是Intel Core 2上的Ubuntu 11.10:
$ uname -a
Linux 3.0.0-14-generic #23-Ubuntu SMP \
Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
$ cat /proc/cpuinfo | grep Intel
model name : Intel(R) Core(TM)2 Quad CPU Q9300 @ 2.50GHz
$ g++ --version
g++ (Ubuntu/Linaro 4.6.1-9ubuntu3) 4.6.1
谢谢, 安德鲁。
答案 0 :(得分:4)
一种可能的情况,逐步跟踪两个写入线程(W0,W1)和一个读取器线程(R0)。 W0早于W1输入put(),被操作系统或硬件中断,稍后完成。
w0 (core 0) w1 (core 1) r0
t0 ---- --- blocked on occupants.wait() / take
t1 entered put() --- ---
t2 vacancies.wait() entered put() ---
t3 got new_head = 1 vacancies.wait() ---
t4 <interrupted by OS> got new_head = 2 ---
t5 written 1 at cell[2] ---
t6 occupants.post(); ---
t7 exited put() waked up
t8 --- got new_tail = 1
t9 <still in interrupt> --- read 0 from ceil[1] !! corruption !!
t10 written 1 at cell[1]
t11 occupants.post();
t12 exited put()
答案 1 :(得分:1)
从设计的角度来看,我会将整个队列视为共享资源,并使用一个互斥锁保护它。
作家执行以下操作:
读者执行以下操作:
答案 2 :(得分:0)
我有一个理论。这是一个循环队列,因此一个阅读线程可能会被重叠。假设读者需要索引0.在它执行任何操作之前它会丢失CPU。另一个读取器线程获取索引1,然后是2,然后是3 ...然后是7,然后是0.第一个读取器唤醒并且两个线程都认为它们对索引0具有独占访问权限。不确定如何证明它。希望有所帮助。