CCriticalSection与CSingleLock

CCriticalSection与CSingleLockCCriticalSectionAnobjectofclassCCriticalSectionrepresentsa“criticalsection”—asynchronizationobjectthatallowsonethreadatatimetoaccessaresourceorsectionofcode.Criticalse

大家好,又见面了,我是你们的朋友全栈君。

CCriticalSection

CCriticalSection与CSingleLock

An object of class CCriticalSection represents a “critical section” — a synchronization object that allows one thread at a time to access a resource or section of code. Critical sections are useful when only one thread at a time can be allowed to modify data or some other controlled resource. For example, adding nodes to a linked list is a process that should only be allowed by one thread at a time. By using a CCriticalSection object to control the linked list, only one thread at a time can gain access to the list.

Critical sections are used instead of mutexes when speed is critical and the resource will not be used across process boundaries. For more information on using mutexes in MFC, see CMutex.

To use a CCriticalSection object, construct the CCriticalSection object when it is needed. You can then access the critical section when the constructor returns. Call Unlock when you are done accessing the critical section.

To access a resource controlled by a CCriticalSection object in this manner, first create a variable of type CSingleLock in your resource’s access member function. Then call the lock object’s Lock member function (for example, CSingleLock::Lock). At this point, your thread will either gain access to the resource, wait for the resource to be released and gain access, or wait for the resource to be released and time out, failing to gain access to the resource. In any case, your resource has been accessed in a thread-safe manner. To release the resource, use the lock object’s Unlock member function (for example, CSingleLock::Unlock), or allow the lock object to fall out of scope.

Alternatively, you can create a CCriticalSection object stand-alone, and access it explicitly before attempting to access the controlled resource. This method, while clearer to someone reading your source code, is more prone to error as you must remember to lock and unlock the critical section before and after access.

For more information on using CCriticalSection objects, see the articleMultithreading: How to Use the Synchronization Classes in Visual C++ Programmer’s Guide.

#include <afxmt.h>


        临界段CCriticalSection可以单独使用,也可以和CSingleLock使用,从性能上讲,临界段要优于互斥量,它是一个用于同步的对象,同一时刻只允许一个线程存取资源或代码区。临界段在控制一次只允许一个线程修改数据或其它的控制资源时非常有用,例如在链表中增加一个结点就只允许一次一个线程进行。通过使用临界段来控制链表,就可以达到这个目的。它就像是一把钥匙,哪个线程获得了它就获得了运行线程的权力,而把其他线程统统阻塞。使用是临界段要先定义在一个全局变量,比如在一个类中声明为数据成员、静态变量、或全局变量。临界段使用一个就够了,用时lock,要保护的资源放这里,不用时unlock,资源不再受保护。CCriticalSection是对CRITICAL_SECTION的封装。

        临界段

CCriticalSection Class Members

Construction

CCriticalSection Constructs a CCriticalSection object.

Methods

Unlock Releases the CCriticalSection object.

virtual BOOL Unlock( );

Return Value

Nonzero if the CCriticalSection object was owned by the thread and the release was successful; otherwise 0.

Remarks

Releases the CCriticalSection object for use by another thread. If the CCriticalSection is being used stand-alone, Unlock must be called immediately after completing use of the resource controlled by the critical section. If a CSingleLock object is being used, CCriticalSection::Unlock will be called by the lock object’s Unlock member function.

Lock Use to gain access to the CCriticalSection object.

BOOL Lock( );  //不带超时参数

BOOL Lock( DWORD dwTimeout ); //带超时参数

Return Value

Nonzero if the function was successful; otherwise 0.

Parameters

dwTimeout

Lock ignores this parameter value.

Remarks

Call this member function to gain access to the critical section object. Lock is a blocking call that will not return until the critical section object is signaled (becomes available).

If timed waits are necessary, you can use a CMutex object instead of a CCriticalSection object.

CSingleLock

CSingleLock does not have a base class.

An object of class CSingleLock represents the access-control mechanism used in controlling access to a resource in a multithreaded program. In order to use the synchronization classes CSemaphore, CMutex, CCriticalSection, and CEvent, you must create either a CSingleLock or CMultiLock object to wait on and release the synchronization object. Use CSingleLock when you only need to wait on one object at a time. Use CMultiLock when there are multiple objects that you could use at a particular time.

To use a CSingleLock object, call its constructor inside a member function in the controlled resource’s class. Then call the IsLocked member function to determine if the resource is available. If it is, continue with the remainder of the member function. If the resource is unavailable, either wait for a specified amount of time for the resource to be released, or return failure. After use of the resource is complete, either call the Unlock function if the CSingleLock object is to be used again, or allow the CSingleLock object to be destroyed.

CSingleLock objects require the presence of an object derived from CSyncObject. This is usually a data member of the controlled resource’s class. For more information on how to use CSingleLock objects, see the articleMultithreading: How to Use the Synchronization Classes in Visual C++ Programmer’s Guide.

#include <afxmt.h>

一个CSingleLock类对象代表一种访问控制机制,这种机制用于控制在一个多线程程序中对一个资源的访问。为了使用同步类CSemaphore,CMutex,CCriticalSection和CEvent,必须创建一个CSingleLock或CMultiLock对象来等待和释放这个同步对象。当每次等待一个对象时,可以使用CSingleLock,当在一个特别的时候你可以使用多个对象时,可以使用CMultiLock。


#include <iostream.h>
#include <afxmt.h>
#include <Afxwin.h>

UINT Fun1Proc(
  LPVOID lpParameter   // thread data
);

UINT Fun2Proc(
  LPVOID lpParameter   // thread data
);

int tickets=100;
CCriticalSection g_CriticalSection;

void main()
{
	AfxBeginThread(Fun1Proc,NULL);
	AfxBeginThread(Fun2Proc,NULL);
	Sleep(4000);
}

UINT Fun1Proc(
  LPVOID lpParameter   // thread data
)
{
	while(TRUE)
	{
		//g_CriticalSection.Lock();
		CSingleLock sLock(&g_CriticalSection);
		sLock.Lock();
		if(tickets>0)
		{
			Sleep(1);
			cout<<"thread1 sell ticket : "<<tickets--<<endl;
		}
		else
			break;
		//g_CriticalSection.Unlock();
		sLock.Unlock();
	}
	cout<<"thread1 is running!"<<endl;
	return 0;
}

UINT Fun2Proc(
  LPVOID lpParameter   // thread data
)
{
	
	while(TRUE)
	{
		//g_CriticalSection.Lock();
		CSingleLock sLock(&g_CriticalSection);
		sLock.Lock();
		if(tickets>0)
		{
			Sleep(1);
			cout<<"thread2 sell ticket : "<<tickets--<<endl;
		}
		else
			break;
		//g_CriticalSection.Unlock();
		sLock.Unlock();
	}
	cout<<"thread2 is running!"<<endl;
	return 0;
}

CCriticalSection与CSingleLock

版权声明:本文内容由互联网用户自发贡献,该文观点仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请联系我们举报,一经查实,本站将立刻删除。

发布者:全栈程序员-站长,转载请注明出处:https://javaforall.net/162022.html原文链接:https://javaforall.net

(0)
全栈程序员-站长的头像全栈程序员-站长


相关推荐

  • 如何查询手机当前基站编号信息呢_基站实测

    如何查询手机当前基站编号信息呢_基站实测Android:拨号*#*#4636#*#*进入手机信息工程模式后查看。iPhone:拨号*3001#12345#*进入FieldTest,LAC(MMInfo>ServingPLMN),3Gcellid(UMTSCellEnvironment>UMTSRRInfo),2Gcellid(GSMCellEnvironment>GSMCellInfo>

    2025年7月5日
    4
  • php工厂模式详解

    php工厂模式详解工厂类就是一个专门用来创建其它对象的类,工厂类在多态性编程实践中是非常重要的。它允许动态替换类,修改配置,会使应用程序更加灵活。掌握工厂模式对Web开发是必不可少的。工厂模式通常用来返回类似接口的不同的类,工厂的一种常见用法就是创建多态的提供者。通常工厂模式有一个关键的构造,即一般被命名为factory的静态方法。这个静态方法可以接受任意数量的参数,并且必须返回一个对象。P

    2022年7月25日
    9
  • CentOS 7 yum卸载jdk、安装jdk以及配置jdk环境

    CentOS 7 yum卸载jdk、安装jdk以及配置jdk环境CentOS7yum卸载jdk、安装jdk以及配置jdk环境查看是否已经安装jdk通过命令查询是否已经安装jdk//括号中选择一个即可yumlistinstalled|grep[java][jdk]运行结果类似下图则说明系统已经存在jdk,可卸载卸载jdk(若未存在jdk不用执行)卸载的jdk按已存在的jdk版本进行卸载,示例为jdk1.8.0,不知版本号可观上图…

    2022年5月25日
    42
  • java gridbagconstraints_GridBagConstraints

    java gridbagconstraints_GridBagConstraintsGridBagConstraintsjavaGui|2014-05-1412:54:00|阅读1737次|评论(1)importjavax.swing.*;importjava.awt.*;publicclassdemo_7{publicstaticvoidmain(String[]args){demo_7_1test=newdemo_7_1();}}clas…

    2022年9月10日
    3
  • 利用matlab画图(r语言能画出哪些图)

    clearallcloseallloadyi.txta=yi;b={‘北京”天津”石家庄”唐山”秦皇岛”太原”呼和浩特”包头’…’沈阳”大连”丹东”锦州”长春”吉林’…

    2022年4月17日
    41
  • quartz调度问题 没报错也没停止运行 Scheduler class: ‘org.quartz.core.QuartzScheduler‘ – running locally

    quartz调度问题 没报错也没停止运行 Scheduler class: ‘org.quartz.core.QuartzScheduler‘ – running locallySchedulerclass:‘org.quartz.core.QuartzScheduler’-runninglocally.NOTSTARTED.Currentlyinstandbymode.Numberofjobsexecuted:0Usingthreadpool‘org.quartz.simpl.SimpleThreadPool’-with20…

    2022年7月27日
    5

发表回复

您的邮箱地址不会被公开。 必填项已用 * 标注

关注全栈程序员社区公众号