共享内存 - 读写锁

2014-04-30 10:51:24 497 阅读 AI 写同款 · GEO 优化AI 选题数据监测一键分发 ›

linux posix 读写锁+共享内存demo ////////////////////////////////////////////////////server.c////////////////////////////////////////////////////////////////////// #include #include #include #include #include #include 阅读详情

问题描述：整个项目采用多进程设计，多进程之间采用共享内存进行通信。通信进程会将采集数据更新到共享内存，其它多个进程都需要从共享内存中读取数据。这样的“一个进程写、多个进程读”的模型，需要采用读写锁来提高访问效率。请问大家用过这种进程间的读写锁吗？单个进程内的多个线程的读写锁比较容易，那多个进程如何操作同一个读写锁？类似于互斥量可以有一个名字参数，这样多个进程可以保证操作的是同一个互斥量。

...全文

linux读写锁_共享内存读写锁（版权归原文作者所有，侵权留言联系删除）原文作者：全栈程序员站长。阅读详情

zhuyf87

C++ 语言 65,214 成员 250,514 内容

+ 关注 + 加入社区

切换为时间正序

luotuo44 2014-04-30

打赏
举报

《APUE》和《Windows核心编程》都没有说到可以用于进程间的读写锁

我还在迷路 2014-04-30

打赏
举报

进来学习~~

shenchenman 2014-04-30

打赏
举报

用一个唯一进程控制内存读写，需要资源的都同该进程交互。参考linux管道进程的实现

赵4老师 2014-04-30

打赏
举报

_locking Locks or unlocks bytes of a file. int _locking( int handle, int mode, long nbytes ); Routine Required Header Optional Headers Compatibility _locking <io.h> and <sys/locking.h> <errno.h> Win 95, Win NT For additional compatibility information, see Compatibility in the Introduction. Libraries LIBC.LIB Single thread static library, retail version LIBCMT.LIB Multithread static library, retail version MSVCRT.LIB Import library for MSVCRT.DLL, retail version Return Value _locking returns 0 if successful. A return value of –1 indicates failure, in which case errno is set to one of the following values: EACCES Locking violation (file already locked or unlocked). EBADF Invalid file handle. EDEADLOCK Locking violation. Returned when the _LK_LOCK or _LK_RLCK flag is specified and the file cannot be locked after 10 attempts. EINVAL An invalid argument was given to _locking. Parameters handle File handle mode Locking action to perform nbytes Number of bytes to lock Remarks The _locking function locks or unlocks nbytes bytes of the file specified by handle. Locking bytes in a file prevents access to those bytes by other processes. All locking or unlocking begins at the current position of the file pointer and proceeds for the next nbytes bytes. It is possible to lock bytes past end of file. mode must be one of the following manifest constants, which are defined in LOCKING.H: _LK_LOCK Locks the specified bytes. If the bytes cannot be locked, the program immediately tries again after 1 second. If, after 10 attempts, the bytes cannot be locked, the constant returns an error. _LK_NBLCK Locks the specified bytes. If the bytes cannot be locked, the constant returns an error. _LK_NBRLCK Same as _LK_NBLCK. _LK_RLCK Same as _LK_LOCK. _LK_UNLCK Unlocks the specified bytes, which must have been previously locked. Multiple regions of a file that do not overlap can be locked. A region being unlocked must have been previously locked. _locking does not merge adjacent regions; if two locked regions are adjacent, each region must be unlocked separately. Regions should be locked only briefly and should be unlocked before closing a file or exiting the program. Example /* LOCKING.C: This program opens a file with sharing. It locks * some bytes before reading them, then unlocks them. Note that the * program works correctly only if the file exists. */ #include <io.h> #include <sys/types.h> #include <sys/stat.h> #include <sys/locking.h> #include <share.h> #include <fcntl.h> #include <stdio.h> #include <stdlib.h> void main( void ) { int fh, numread; char buffer[40]; /* Quit if can't open file or system doesn't * support sharing. */ fh = _sopen( "locking.c", _O_RDWR, _SH_DENYNO, _S_IREAD | _S_IWRITE ); if( fh == -1 ) exit( 1 ); /* Lock some bytes and read them. Then unlock. */ if( _locking( fh, LK_NBLCK, 30L ) != -1 ) { printf( "No one can change these bytes while I'm reading them\n" ); numread = _read( fh, buffer, 30 ); printf( "%d bytes read: %.30s\n", numread, buffer ); lseek( fh, 0L, SEEK_SET ); _locking( fh, LK_UNLCK, 30L ); printf( "Now I'm done. Do what you will with them\n" ); } else perror( "Locking failed\n" ); _close( fh ); } Output No one can change these bytes while I'm reading them 30 bytes read: /* LOCKING.C: This program ope Now I'm done. Do what you will with them File Handling Routines See Also _creat, _open

tbwork 2014-04-30

打赏
举报

之前写驱动的时候用到过共享内存，是把系统内存和自己的程序关联起来。大致步骤是，好像有个Map函数，把某个共享内存映射到不同进程的自己的空间中。至于读写锁，应该可以自己控制。如果只有一个写进程，写进程在开始写时，就把该段内存的权限设置为只写，不允许读，读可以多个一起读。如果有多个写进程，我抛砖引玉下吧，可行度不一定高：可以设置一个唯一逻辑写进程，其他的写进程全部发送给这个写进程，以队列的形式，进行写。

共享内存 - 读写锁

相关推荐