pthread_mutex_lock in ANSI C vs using Atomic builtins of GCC


 
Thread Tools Search this Thread
Top Forums Programming pthread_mutex_lock in ANSI C vs using Atomic builtins of GCC
# 1  
Old 08-25-2010
pthread_mutex_lock in ANSI C vs using Atomic builtins of GCC

I have a program which has 7-8 threads, and lots of shared variables; these variables (and also they may not the primitive type, they may be enum or struct ), then they may read/write by different threads at the same time.

Now, my design is like this,

Code:
typedef unsigned short int UINT16;
struct STRUCT {
  UINT16 uint16;
  int INT;
}
enum ENUM = { ... };

/* Shared Variables. */
struct STRUCT Shared_VariableA;
enum ENUM Shared_VariableB;

UINT16 GetVA () {
    pthread_mutex_lock( &_L_LOCK );
        UINT16 TMP = Shared_VariableA.uint16;
    pthread_mutex_lock( &_L_LOCK );
    return TMP;
}

void SetVA ( UINT16 in ) {
     pthread_mutex_lock( &_L_LOCK );
         Shared_VariableA.uint16 = in;
     pthread_mutex_lock( &_L_LOCK );
 }

Is it enough to guarantee that only a thread can write/read shared variables at the same time?

How about the following method? Same?
From the reference : Techie Stuff Atomic Operations

Code:
/* Initialization. */
atomic_t uint16 = ATOMIC_INIT ( 0 );

UINT16 GetVA () {
         UINT16 TMP = atomic_read( &uint16 );  /* Force convert 'int' to UINT16 since atomic_read() returns an int (32 bits). */
        return TMP;
 }
 
 void SetVA ( UINT16 in ) {
       atomic_set( &uint16,in );
  }

Whether getVA() will return an arbitrary value when SetVA() is running by other threads?
# 2  
Old 08-25-2010
Yes, the pthread solution more than sufficiently protects it. (A pthread_rwlock would let readers operate at the same time and only block them for writes.)

If the gcc atomic operations are truly atomic, getva shouldn't ever return garbage.
# 3  
Old 08-26-2010
I assume that this is a typo - the second pthread_mutex_lock() should be a pthread_mutex_unlock().
Code:
     pthread_mutex_lock( &_L_LOCK );
         Shared_VariableA.uint16 = in;
     pthread_mutex_lock( &_L_LOCK );

This User Gave Thanks to fpmurphy For This Post:
# 4  
Old 08-26-2010
Quote:
Originally Posted by Corona688
Yes, the pthread solution more than sufficiently protects it. (A pthread_rwlock would let readers operate at the same time and only block them for writes.)

If the gcc atomic operations are truly atomic, getva shouldn't ever return garbage.
Code:
/* Shared Variables. */
struct STRUCT Shared_VariableA;
enum ENUM Shared_VariableB;

UINT16 GetVA () {
    pthread_mutex_lock( &_L_LOCK );
        UINT16 TMP = Shared_VariableA.uint16;
    pthread_mutex_unlock( &_L_LOCK );
    return TMP;
}

I have a question, if a shared variable may read/write by some threads and with pthread_mutex_lock(), is the variable requires a 'volatile'?
e.g.
Code:
volatile struct STRUCT Shared_VariableA;



---------- Post updated at 01:03 PM ---------- Previous update was at 01:02 PM ----------

I am sorry, it should be:
Code:
     pthread_mutex_lock( &_L_LOCK );
         Shared_VariableA.uint16 = in;
     pthread_mutex_unlock( &_L_LOCK );

Quote:
Originally Posted by fpmurphy
I assume that this is a typo - the second pthread_mutex_lock() should be a pthread_mutex_unlock().
Code:
     pthread_mutex_lock( &_L_LOCK );
         Shared_VariableA.uint16 = in;
     pthread_mutex_lock( &_L_LOCK );

# 5  
Old 08-26-2010
If properly bounded by mutexes(or other synchronization calls) it shouldn't need "volatile". Atomic operations might still need it.
This User Gave Thanks to Corona688 For This Post:
# 6  
Old 08-26-2010
It is possible create a variable with "volatile" but it is not a primitive type, e.g.

Code:
struct STRUCT {
  volatile int S1;
  volatile char S2;
  volatile  unsigned short int S3;
}
volatile struct STRUCT v1;
volatile enum ENUM v2;
volatile char V3;
volatile unsigned int V4;

v1->S1 = 1;
v1->S2 = 2;
v1->S3 = 3;

v2 = 4;

v3 = 5;

v4 = 6;

Are above operations atomic?
Is any case that "volatile" can not guarantee atomic operation?
# 7  
Old 08-26-2010
"volatile" has nothing to do with atomic, "volatile" just tells the compiler to never assume that variable is whatever it set it to last. (otherwise, it might assume it never changes and hardcode it in the instructions.)

No variables (except the gcc atomic extensions) are guaranteed to be atomic, at all, ever. There's other problems than being atomic, too -- on a multicore system, one core might have a different copy of the memory still in cache, causing even "volatile" to fail. You need to inform other cores you're modifying values out from under them, which is what memory barriers are for. pthreads does memory barriers for you. I don't know if gcc atomic ops do.

Last edited by Corona688; 08-26-2010 at 05:33 PM..
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Shell and bash builtins...

Not sure if this is the right forum but I have collated a listing of shell and bash builtins. Builtins is a loose word and may include the '/bin' drawer/folder/directory but NOT any others in the path list. In the case of my Macbook Pro, OSX 10.7.5 the enabled internals is also listed... ... (1 Reply)
Discussion started by: wisecracker
1 Replies

2. Programming

Using ANSI color codes in gcc compiled program

I have put some yellow color codes and works well. I call the funstion using print_usage(stderr, 0); I would like to know if there is any way, to store the ansi color codes in variables and then call them inside fprintf. Or have a format followed by the strings I want to output. ... (5 Replies)
Discussion started by: kristinu
5 Replies

3. UNIX for Dummies Questions & Answers

Why does /bin contain binaries for builtins?

Why do shell builtins like echo and pwd have binaries in /bin? When I do which pwd, I get the one in /bin. that means that I am not using the builtin version? What determines which one gets used? Is the which command a definitive way to determine what is being run when I enter pwd? (16 Replies)
Discussion started by: glev2005
16 Replies

4. UNIX for Advanced & Expert Users

Writing Custom Builtins for KSH93

I am looking to create some ksh93 extensions using the custom builtin feature. I can successfully create a builtin function, load it using the builtin -f command and get an output. However, I want to get/set values of KSH variables from within my built-in. For example, lets say I am creating... (2 Replies)
Discussion started by: a_programmer
2 Replies

5. Programming

why the implementatoin of Bakery algorithm in ANSI C does not work in ANSI C

I follow the description of wiki (Lamport's bakery algorithm - Wikipedia, the free encyclopedia), then implement that algorithm in C, but it doesn't work, Starving is still here, is the implementation worry? Only print out: Thread ID: 0 START! Thread ID: 0 END! Thread ID: 0 START!... (2 Replies)
Discussion started by: sehang
2 Replies

6. Shell Programming and Scripting

program name and function name builtins

Hi Is there a way to get the program/script name or function name usng built ins. Like in many languages arg holds the program name regards (2 Replies)
Discussion started by: xiamin
2 Replies

7. Programming

Interesting issue with pthread_mutex_lock and siglongjmp in AIX 5.3 (and no other OS)

Executive summary: Code (posted below) cores in AIX 5.3, despite being compiled and run successfully on several other operating systems. Code is attempting to verify that pthread_mutex_lock can be successfully aborted by siglongjmp. I do not believe this is an unreasonable requirement. If... (1 Reply)
Discussion started by: DreamWarrior
1 Replies

8. Programming

pthread_rwlock_lock vs pthread_mutex_lock

I have been wondering what the difference between pthread_rwlock_lock and pthread_mutex_lock is. Both these routines acquire an exclusive rw lock on an enclosed region. So I performed a simple experiment in which I execute both these routines multiple times in a loop. Here are the results:... (1 Reply)
Discussion started by: kmehta
1 Replies

9. Shell Programming and Scripting

Convert file from Unix - ANSI to PC - ANSI

Hi, I am creating a file in Unix using a shell script. The file is getting created in the Unix - ANSI format. My requirement is to convert it to the PC - ANSI format. Can anyone tell me how to do this? Thanks, Sunil (0 Replies)
Discussion started by: ssmallya
0 Replies
Login or Register to Ask a Question