KR20200020485A - Apparatus and Method for Managing Resource of OS System - Google Patents

Abstract

The present invention relates to a resource management apparatus of an operating system and a method thereof. According to the present invention, the apparatus comprises a management control part that uses a resource list including information on a resource type and a resource request target for a system resource access of an application program and manages system resources by using an abstracted resource list derived from the resource list for system resource monitoring of an operating system. Therefore, the apparatus can efficiently manage resources while preventing performance degradation of the operating system by accessing system resources by using a resource list for the system resources in an application program and accessing the system resources by using the abstracted resource list derived from the resource list in the system resource monitoring.

Description

Apparatus and Method for Managing Resource of OS System

The present invention relates to an apparatus and method for managing a resource of an operating system, and more particularly, to a resource management of an operating system system capable of efficiently using and managing resources by separating a resource access area of an application program and a resource access area of a monitoring program. An apparatus and method are disclosed.

In recent years, the performance of various embedded systems has increased due to the complexity of the system. Accordingly, the installation of a real-time operating system (RTOS) has become common. A real-time operating system is an operating system that can be applied to embedded systems that require high reliability and stability, such as aerospace components, medical equipment, or industrial control systems. It provides the basic functions necessary for configuring real-time software, and has clearly defined operations and input / output. It can perform the function of managing resources strictly so that it can be achieved within the time limit.

Such a real-time operating system can provide monitoring of resources shared throughout the system and kernel resources, which are the exclusive resources of the application. The monitoring of resources displays a list of the resources currently used by the application and the history of resource usage. As a real-time operating system directly accesses and uses kernel resources, the process of monitoring kernel resources is important.

As such, monitoring kernel resources has a great impact on the performance of a real-time operating system because it is possible to know what kind of resources are used in an application and how much.

However, in a real-time operating system having a single core processor, since the processor executes one thread at a time, when the kernel resource is monitored, the application is stopped and there is no contention state for the kernel resource. Because the processing architecture executes as many threads as there are processors at a time, there is a race for kernel resources when monitoring and applications access kernel resources at the same time.

As such, when the monitoring and application programs are in a race for kernel resources due to the characteristics of the real-time operating system, there is a problem affecting the integrity as well as the performance of the real-time operating system.

In addition, when monitoring uses the kernel resource first, the application maintains the wait state until the kernel resource is occupied. In this case, there is a problem that a lot of resource occupancy waiting costs are incurred. For example, an application may be more expensive and require more access to kernel resources, such as reads or writes, which are frequently requested. If monitoring prevents an application from accessing kernel resources, then reads and writes Due to frequent delays in function, there is a problem that a large amount of resource occupancy waiting costs are incurred.

Korean Laid-Open Patent Publication No. 2007-0037427 (published 2007. 04. 04.) Korean Laid-Open Patent Publication No. 2005-0033327 (published 2005. 04. 12)

Therefore, the technical problem to be solved by the present invention is to access the system resources using the resource list for the system resources in the application program, the system resource monitoring to access the system resources using the abstracted resource list derived from the resource list The present invention provides a resource management apparatus and method for an operating system system that can efficiently manage resources while preventing performance degradation.

In addition to the objects explicitly stated, the present invention also includes other objects that can be achieved from the configurations of the present invention described below.

The resource management apparatus of the operating system system according to an embodiment of the present invention for solving the above technical problem uses a resource list including information on the type of resource and the resource request target for accessing the system resource of the application program, The system resource monitoring includes a management control unit that manages system resources using an abstracted resource list derived from the resource list.

The apparatus may further include a resource list generator configured to generate a resource list for a kernel resource that is a monitoring target of an operating system among the system resources.

The apparatus may further include an abstraction list generator for extracting resource information from the kernel resource included in the generated resource list and generating the abstracted resource list.

The management controller processes a kernel resource request of the application program by using the resource list in order to secure the real-time property of the application in a multi-core operating system, and extracts the abstracted resource list derived from the resource list. It can handle kernel resource requests for monitoring.

When the management controller receives a request for allocation of a kernel resource from the application program, the resource control module performs management for registering the kernel resource in the resource list according to the request, and the information about the performed management is abstracted. It may include a synchronization module to reflect in the resource list.

When the resource allocation module receives a request for allocation of a kernel resource from the application program, the resource allocation module adds node information on a type of kernel resource and a kernel resource request target to which the allocation is requested, to the resource list, and wherein the node information is added. You can update the resource list.

The synchronization module may store information on the management performed in a buffer and reflect the information on the abstracted resource list.

The synchronization module may determine whether there is information stored in the buffer, and if the information is stored in the buffer, the synchronization module may update the information stored in the buffer to the abstracted resource list.

The management controller may further include a resource release module for deleting the kernel resource from the resource list in response to the request for release of a kernel resource from the application program.

On the other hand, in the resource management method of the operating system according to an embodiment of the present invention, generating a resource list including information on the type of system resources and the request target of the system resources, resource information from the system resources included in the resource list Generating the abstracted resource list by using the extracted resource list; and using the resource list for system resource access of an application program, and using the abstracted resource list derived from the resource list for system resource monitoring of an operating system. Managing system resources.

The generating of the resource list may generate a resource list of a kernel resource that is a monitoring target of an operating system among the system resources.

The generating of the abstracted resource list may generate the abstracted resource list by extracting resource information from a kernel resource included in the generated resource list.

The managing of the system resource may include: performing management to register the kernel resource in the resource list according to the request when receiving a request for allocation of a kernel resource from the application program; and receiving information about the performed management. And reflecting the abstracted resource list.

The reflecting of the abstracted resource list may determine whether there is information stored in the buffer, and when the information is stored in the buffer, the information stored in the buffer may be updated to the abstracted resource list.

The managing of the system resource may further include deleting the kernel resource from the resource list in response to the request for the release of the kernel resource from the application program.

As described above, according to an apparatus and method for managing a resource of an operating system according to an embodiment of the present invention, an application accesses a system resource using a resource list of system resources, and in a system resource monitoring, an abstracted resource derived from a resource list By accessing system resources using a list, it is possible to efficiently manage system resources while preventing performance degradation of the operating system.

As such, the application program separates the function of accessing the system resource to use the system resource and the function of accessing the system resource to access the system resource and uses the system resource to implement the system resource to efficiently manage the system resource. There is an advantage to improve the reliability of the operating system by ensuring the integrity of resources.

On the other hand, the effects of the present invention are not limited to those described above, and other effects that can be derived from the configuration of the present invention described below are also included in the effects of the present invention.

1 is a schematic structural diagram of an operating system system according to an embodiment of the present invention.
FIG. 2 is a detailed configuration diagram of the resource management apparatus shown in FIG. 1.
3 is an operation flowchart illustrating a resource management process of an operating system system according to an embodiment of the present invention.
4 is a flowchart illustrating a process of processing a resource using a resource list according to an embodiment of the present invention.
5 is a flowchart illustrating a process of monitoring a resource using an abstracted resource list according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention.

FIG. 1 is a schematic configuration diagram of an operating system system according to an embodiment of the present invention, and FIG. 2 is a detailed configuration diagram of a resource management apparatus shown in FIG.

As shown in FIG. 1 and FIG. 2, the operating system system 1 provides a base environment for the execution of the application program 50 and controls a hardware device to serve as an interface between the application program 50 and the hardware device. An operating system can be implemented. Here, the application program 50 may include not only an application written to perform a specific request of a user who uses a hardware device through a user interface provided by the operating system, but also all software that may be executed in the operating system.

In addition, the operating system system 1 may include a resource management apparatus 100 that manages system resources such as a central processing unit, an input / output device, a network device, or a storage device required for the execution of the application program 50.

The resource management apparatus 100 includes a resource list generator 110, an abstraction list generator 120, and a management controller 130.

The resource list generator 110 may generate a resource list including information on the type of system resource and a request target of the system resource. That is, the resource list generation unit 110 may provide information on the types of system resources such as a central processing unit, an input / output device, a network device, or a storage device, which can be accessed and used by the application program, and the targets of requesting system resources. (Eg, identification information of an application program requesting system resources) may generate a resource list. In particular, the resource list generator 110 may generate a resource list for a kernel resource, which is a monitoring target of the operating system, from among system resources. Here, the kernel is the most important core of the computer operating system, and is a Windows or Linux. Alternatively, when an operating system such as Unix boots, the hardware device can be controlled based on an existing configuration file, and process management, memory management, task management, or system management can be performed. Types of kernel resources may include memory, semaphores, or inter-processor communication (IPC).

The abstraction list generator 120 may generate an abstracted resource list derived from the resource list.

In more detail, the abstraction list generating unit 120 may generate an abstracted resource list by extracting information of kernel resources necessary for monitoring from kernel resources included in the resource list generated by the resource list generating unit 110. Here, abstraction is a task that separates only important and relevant parts of a given system to make it simple and easy to understand, and abstracted resource list is a separate list by extracting kernel resource information necessary for monitoring from the resource list for kernel resources. Say what made it. As such, the abstraction list generation unit 120 may generate an abstracted resource list through an abstraction operation of extracting information of kernel resources related to monitoring from the resource list.

The management controller 130 controls the management of system resources by using a resource list for accessing system resources of the application 50 and using an abstracted resource list derived from the resource list for monitoring system resources of the operating system. can do.

In more detail, the management controller 130 processes the kernel resource request of the application program 50 by using the resource list in order to secure the real time of the application program 50 in the multi-core operating system system, and abstracted resources. The list can be used to handle kernel resource requests for monitoring. Unlike a general-purpose operating system, a real-time operating system operates in an embedded system. Therefore, the real-time operating system should start operating when power is applied. In particular, the more critical the fast operation after power-up, such as vehicle airplanes or medical devices, the more stringent the time limit, the kernel simultaneously for resource usage and resource monitoring of the application 50 in a multi-core real-time operating system When accessing a resource, an operation of the application program 50 may be delayed, which may greatly affect the performance of an operating system. Therefore, when the management controller 130 receives a kernel resource request from the application 50, the application 50 accesses the resource list to use the kernel resource, and in monitoring the kernel resource, the management resource 130 accesses the abstracted resource list. By using the kernel resources to separate the access area of the application program 50 and the access area for monitoring the kernel resources, the application 50 can use the kernel resources immediately without time delay, the application 50 is You can monitor kernel resources even if you use kernel resources.

Here, when monitoring the kernel resource, the data to be monitored differs according to the type of kernel resource. For example, when the kernel resource is a memory, an allocation size or a free size of how much memory is allocated and released is monitored. Kernel resources can monitor lock / unlock, lock count for semaphores, and maximum message size if kernel resources are IPC. The number of queued messages, the number of sent messages, and the number of sent messages can be monitored.

As such, the operating system system 1 may provide a monitoring function for the kernel resources while allowing the application 50 to use the kernel resources. By checking how much kernel resources are used, you can manage kernel resources efficiently while preventing performance degradation of the real-time operating system.

More specifically, the management controller 130 may include a resource allocation module 131, a synchronization module 133, and a resource release module 135.

When the resource allocation module 131 receives a request for allocation of a kernel resource from the application program 50, the resource allocation module 131 may perform management of registering the kernel resource in the resource list according to the request. That is, when the application 50 requests access to allocate a specific kernel resource, the resource allocation module 131 adds the kernel resource that requested the allocation to the resource list to allow access to the kernel resource. .

When the resource allocation module 131 receives a request for allocating a kernel resource from the application program 50, the resource allocation module 131 adds node information about the type of the kernel resource allocated to the resource list and a target of the kernel resource request, and adds node information. You can update the list. That is, when the resource allocation module 131 receives a request for allocating a kernel resource from the application 50, the type of the kernel resource and the kernel resource request are recognized so that the application 50 knows what kind of kernel resource has been allocated. You can add node information that stores information about the target.

On the other hand, when the resource allocation module 131 receives a kernel resource allocation request from the application program 50, the resource allocation module 131 may lock the resource list so that only the application program 50 that requests the kernel resource allocation may be updated. In this case, when the resource allocation module 131 is requested to allocate or release a kernel resource, the resource list may be accessed and updated only by the application 50 requesting the allocation or release, and the resource list may be accessed by another application. Can be controlled so that For example, if another application 50 accesses and uses the resource list before updating the resource list in the application 50 requesting the allocation, the internal structure of the operating system may be broken, and thus all kernel resource updates are completed. Until another application 50 locks the access to the resource list, and when the update of the corresponding resource list is completed, the lock of the resource list may be released. In this way, by locking or unlocking the resource list, the resource list can be kept synchronized even if the plurality of applications use the resource list.

The synchronization module 133 may reflect information on management performed by the resource allocation module 131 in the abstracted resource list. That is, when the state of the kernel resource stored in the resource list is changed, the synchronization module 133 may equally reflect the changed state information of the kernel resource in the abstracted resource list.

To this end, the synchronization module 133 may store the information on the management (for example, the changed kernel resource state information) in the buffer 70 and reflect the information on the abstracted resource list. If information is stored in the buffer 70, the information stored in the buffer 70 may be updated to an abstracted resource list. That is, when monitoring of kernel resources is requested, first, whether there is information to be applied to the abstracted resource list is checked through the presence or absence of information stored in the buffer 70, and if there is information to be applied to the abstracted resource list, the information is provided. You can update the abstracted resource list. Then, the monitoring function can be performed by extracting the monitored data from the abstracted resource list.

As such, when using the method of storing the information about the management performed in the buffer 70, compared to the method of directly reflecting the information on the management performed in the abstracted list of resources, the time required to save kernel resources The cost of abstraction can be reduced.

In FIG. 2, the buffer 70 is illustrated as being installed inside the resource management apparatus 100, but the present invention is not limited thereto. The buffer 70 may be installed outside the resource management apparatus 100.

When the resource release module 135 is requested to release the kernel resource from the application program 50, the resource release module 135 may delete the kernel resource from the resource list according to the request.

That is, when the application 50 requests the release of the kernel resource, the resource release module 135 may delete the information on the kernel resource in the resource list. Here, releasing the kernel resource may mean a process in which the kernel resource is intentionally reclaimed by the operating system to complete the use of the kernel resource in the application 50 or to execute another application 50 having a high priority. It may be, but is not limited thereto.

Hereinafter, a resource management method of an operating system system according to an embodiment of the present invention will be described.

3 is an operation flowchart illustrating a resource management process of an operating system system according to an embodiment of the present invention.

Referring to FIG. 3, a resource list including information on types of system resources and request targets of system resources may be generated (S100).

That is, the type of system resources such as a central processing unit, an input / output device, a network device, or a storage device that an application can access and use, and information about the target of the system resource request (for example, identification of the application requesting the system resource). Information list) can be created. In particular, it is possible to generate a resource list of kernel resources that are monitored by the operating system among the system resources, where the kernel is the most important part of the computer operating system, and the operating system such as Windows, Linux or Unix can boot. In this case, the hardware device may be controlled based on an existing configuration file, and in addition, process management, memory management, task management, or system management may be performed. Types of kernel resources may include memory, semaphores, or inter-processor communication (IPC).

Next, resource information may be extracted from system resources included in the resource list to generate an abstracted resource list (S200).

In more detail, the abstracted resource list may be generated by extracting information of kernel resources required for monitoring from the kernel resources included in the resource list generated in step 100. Here, abstraction is a task that separates only important and relevant parts of a given system to make it simple and easy to understand, and abstracted resource list is a separate list by extracting kernel resource information necessary for monitoring from the resource list for kernel resources. Say what made it. As such, an abstracted resource list may be generated through an abstraction operation of extracting information of kernel resources related to monitoring from a resource list of kernel resources.

Thereafter, the system resource may be managed using the resource list for accessing the system resource of the application program and the abstracted resource list derived from the resource list for the system resource monitoring of the operating system (S300).

More specifically, in order to secure real-time application of a multi-core operating system, the resource list is used to process the kernel resource request of the application, and the abstracted resource list is used to process the kernel resource request for monitoring. can do. In other words, when accessing kernel resources simultaneously for resource usage and resource monitoring in a multi-core real-time operating system, the operation of the application may be delayed, which may greatly affect the performance of the operating system. When the controller 130 receives a kernel resource request from the application program 50, the control unit 130 accesses the resource list to use the kernel resource. In the monitoring of the kernel resource, the controller 130 accesses the abstracted resource list to access the kernel resource. By using it, the access area of the application program 50 and the access area for monitoring the kernel resource can be separated.

Hereinafter, a method of processing a resource according to a resource allocation or release request of an application program according to an embodiment of the present invention will be described.

4 is a flowchart illustrating an operation of processing a resource using a resource list according to an embodiment of the present invention.

Referring to FIG. 4, upon receiving an access request of a kernel resource from an application program, it may be determined whether the request is an allocation or release request of a kernel resource (S400).

If the request is a kernel resource allocation or release request (S400-Y), a lock on the resource list may be set (S401). At this time, when a kernel resource allocation or release request is made, only the application program requesting the allocation or release can access and update the resource list, and control the access to the resource list from other applications. For example, if another application accesses and uses the resource list before updating the resource list, the application requesting the allocation may break the internal structure of the operating system system. You can lock the list so that it is inaccessible and release the lock of the resource list when the update of the corresponding resource list is completed. As such, even when the resource list is used by a plurality of applications through locking or unlocking the resource list, synchronization of the resource list may be maintained.

Then, it is determined whether the kernel resource allocation request (S402), and in the case of the allocation request of the kernel resource, the kernel resource may be registered in the resource list according to the request (S403).

That is, when an application program requests access to allocate a specific kernel resource, it adds the requested kernel resource to the resource list to allow access to the kernel resource.

When a kernel resource allocation request is received from an application program, node information about a kernel resource type and a kernel resource request target allocated to the resource list may be added, and the resource list to which the node information is added may be updated. For example, when a request is made to allocate a kernel resource from an application, node information containing information on the type of kernel resource and the target of the kernel resource request is stored so that the application knows what kind of kernel resource is requested. Can be.

Next, the lock setting for the resource list may be released (S404), and information on registration of the kernel resource may be reflected on the abstracted resource list (S405). That is, when the state of the kernel resource stored in the resource list is changed, the changed state information of the kernel resource may be controlled to be reflected in the abstracted resource list in the same manner.

More specifically, information about the management performed (for example, the status information of the changed kernel resource) may be stored in a buffer and reflected in the abstracted resource list. At this time, it is determined whether information is stored in the buffer, and the information is stored in the buffer. If so, you can update the information stored in the buffer to an abstracted resource list. In other words, when monitoring of kernel resources is requested, first check whether there is information to be applied to the abstracted resource list through the presence or absence of information stored in the buffer, and if there is information to be applied to the abstracted resource list, the information is abstracted. You can update the list. Then, the monitoring function can be performed by extracting the monitored data from the abstracted resource list.

On the other hand, if the request is not an allocation or release request for kernel resources in step 400 (S400-N), it may be determined whether a request resource exists in the resource list (S406). That is, if the kernel resource requested by the application is in the resource list, and if the resource requested by the application exists in the resource list (S406-Y), the request for the resource may be processed (S407).

On the other hand, if the request is not an allocation request for kernel resources in step 402 (S402-N), it is determined whether the release of the kernel resources (S408), and if the request for release of kernel resources (S408-Y), resources according to the request The kernel resource may be deleted from the list (S409).

In other words, if an application requires the release of a kernel resource, it can delete information about the kernel resource in the resource list, where releasing the kernel resource is such that the application has finished using the kernel resource, or This can mean the deliberate reclaiming of kernel resources from the operating system to run other applications.

5 is a flowchart illustrating an operation of monitoring a resource using an abstracted resource list according to an embodiment of the present invention.

Referring to FIG. 5, when monitoring of kernel resources is requested, it may be determined whether information is stored in a buffer (S500). Here, the information stored in the buffer is information to be applied to the abstracted resource list, and may include, for example, information about the changed kernel resource state.

If the information is stored in the buffer (S500-Y) in step 500, the information stored in the buffer may be reflected in the abstracted resource list (S501).

More specifically, when the monitoring of kernel resources is requested, whether there is information to be applied to the abstracted resource list is checked through the presence or absence of information stored in the buffer, and if there is information to be applied to the abstracted resource list, the information is abstracted. You can update the list. As such, when the information on the management performed is stored in a buffer, the time required for the management can be reduced compared to the method of directly reflecting the management performed on the abstracted resource list. The cost can be reduced.

Next, the monitoring target data may be extracted from the abstracted resource list (S502), and the monitoring target data may be transmitted to perform monitoring (S503).

On the other hand, if the information is not stored in the buffer in step 500, the process proceeds to step 502 to extract the monitoring target data from the abstracted resource list (S502), and transmits the monitoring target data to perform the monitoring (S503). .

Then, it may be determined whether or not the monitoring is terminated (S504) to terminate the monitoring of the resource.

Embodiments of the invention include a computer readable medium containing program instructions for performing various computer-implemented operations. This medium records a program for executing the resource management method of the operating system described above. The media may include, alone or in combination with the program instructions, data files, data structures, and the like. Examples of such media include magnetic media such as hard disks, floppy disks and magnetic tape, optical recording media such as CDs and DVDs, floppy disks and program commands such as magnetic-optical media, ROM, RAM, flash memory, and the like. Hardware devices configured to store and perform such operations. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.

Although the preferred embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1: operating system
100: resource management device
110: resource list generation unit
120: abstraction list generator
130: management control unit
131: resource allocation module
133: synchronization module
135: resource release module

Claims (15)

For accessing system resources of an application, a resource list including information on resource types and resource request targets is used. For monitoring system resources of an operating system, an abstract resource list derived from the resource list is used for system resources. Management control unit to manage
Resource management apparatus of the operating system system including a. In claim 1,
The resource management device of the operating system system further comprises a resource list generating unit for generating a list of resources for the kernel resource that is the monitoring target of the operating system among the system resources. In claim 2,
And an abstraction list generator for extracting resource information from the kernel resources included in the generated resource list and generating the abstracted resource list. In claim 1,
The management control unit,
In the multi-core operating system to process the kernel resource request of the application using the resource list to secure the real-time of the application,
A resource management apparatus of an operating system system that processes a kernel resource request for monitoring by using the abstracted resource list derived from the resource list. In claim 4,
The management control unit,
A resource allocation module for performing management for registering the kernel resource in the resource list according to the request when a request for allocation of a kernel resource is received from the application program;
Device for managing an operating system system including a synchronization module for reflecting the information on the management performed in the abstracted resource list. In claim 5,
The resource allocation module,
When the kernel resource allocation request is received from the application program, node information about a kernel resource request object and a type of the kernel resource requested to be allocated is added to the resource list, and the resource list to which the node information is added is updated. Resource management device of the operating system. In claim 5,
The synchronization module,
Device for managing an operating system system to store the information on the management performed in the buffer to reflect the abstracted resource list. In claim 7,
The synchronization module,
Determine whether there is information stored in the buffer,
And when information is stored in the buffer, updating the information stored in the buffer to the abstracted resource list. In claim 5,
The management control unit,
And a resource release module to delete the kernel resource from the resource list in response to the request for release of a kernel resource from the application program. Generating a resource list including information on the type of system resource and a request target of the system resource,
Extracting resource information from a system resource included in the resource list to generate the abstracted resource list, and
Managing system resources using the resource list for accessing system resources of an application program and using the abstracted resource list derived from the resource list for system resource monitoring of an operating system;
Resource management method of the operating system system comprising a. In claim 10,
Generating the resource list,
A method of managing a resource of an operating system, which generates a resource list of kernel resources that are an object of monitoring of an operating system among the system resources. In claim 11,
Generating the abstracted resource list,
And extracting resource information from a kernel resource included in the generated resource list to generate the abstracted resource list. In claim 12,
Managing the system resources,
Performing a management of registering the kernel resource in the resource list in response to the request for allocation of a kernel resource from the application program, and
And reflecting the information on the management performed in the abstracted resource list. In claim 13,
Reflecting in the abstracted resource list,
Determine the existence of information stored in the buffer,
And when information is stored in the buffer, updating the information stored in the buffer to the abstracted resource list. In claim 13,
Managing the system resources,
And deleting the kernel resource from the resource list when the kernel resource is requested to be released from the application program.

Images