Search Results

Bear in mind though that the "best" case is also the typical one here.

Not a problem here, the idle workers are searching through separate queues.

Fair enough, in rare cases, it could behave...

At start-up I used the pthread_setaffinity_np function. Each pthread exists on its core for the life-time of the application, i.e:


ret_code = pthread_setaffinity_np(thread->tid,...

That's an impressive reply Corona, you made your case very persuasively, but it's not "my case". The problem is you're not aware of the overall system, its context, aims and design (which is not your...

But with those atomic operations I can avoid sending threads to sleep and having to wake them up.

I would agree if no other progress is being made, but to reiterate, the thread-pool I'm building...

I was referring to the older GNU Portable Threads...

GNU Pth - The GNU Portable Threads (http://www.gnu.org/software/pth/pth-manual.html)

"Pth doesn't require any kernel support, but can NOT...

Looks like you're right judging by those results. But if I ran it on 4/8/16/32 etc cores, would it still be the case? I have 4-core at work, I'll try it tomoro. Although if LOCK just causes a...

I've accounted for that possibility in the elaborate design of the "task-queues", (trust me on this).

The "thread-pool" is a customised in design, dedicated for the application sitting atop of...

Noting your help on the Programming forum too!

Are you suggesting then, that if I used such an instruction relatively frequently (say once in a loop of maybe a 100 execution statements, per...

Hi Corona, (small world :))



I hadn't heard of futexes until you mentioned them, but I did some reading and it seems they still use atomic instructions to update shared variables. In that case...

Hi all,

(Hope this is the right forum for this question)

I have some multi-threaded C code (compiled with GCC 4.4.3) which accesses shared variables. Although I've marked those variables with...

Thanks for the heads-up Corona688,

You might be right, but the thing is I had to store the "pthread_t" values in an array anyway, so in my application, after calling pthread_self() I would then...

No. That wouldn't work unfortunately. I'd have to save it in something that I would then need to tag along to every function as a parameter. I don't want to do that because I'm building 2...

I have allocated the memory. I've ran and tested the program and it works without seg-faulting. I'm "pretty" certain that I understand what's going on now with the pointers, although of course I...

"I can't think of a good reason to call pthread_self a lot.
why?"

It's a long story, but basically I need a way of accessing application specific "context" information I have stored which is...

Thanx for your reply,

"you're trying to initialize a struct, from a pointer."

I thought with the typedef...


typedef section_t* region_t[SECTION_LENGTH];
This would mean that the following...

Hi all,

Can anyone provide help with getting the right syntax regarding array/pointers in C in the following code? Can't locate a specific example which clarifies this...

Say I declare a...

Thanks for your replay Corona688.

I found similar code in glibc (tls.h)...


/* Return the TCB address of the current thread. */
# define THREAD_SELF \
...

Hi all,

Is anyone aware of what operations are involved when a call to pthread_self() is made, obtaining the unique thread ID on a Ubuntu system (or even any Linux flavour)?

Specifically, to...