CN105183666A - Scheduling control method, device and system - Google Patents
Scheduling control method, device and system Download PDFInfo
- Publication number
- CN105183666A CN105183666A CN201510583505.XA CN201510583505A CN105183666A CN 105183666 A CN105183666 A CN 105183666A CN 201510583505 A CN201510583505 A CN 201510583505A CN 105183666 A CN105183666 A CN 105183666A
- Authority
- CN
- China
- Prior art keywords
- read
- write requests
- virtual volume
- manager
- controller
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Abstract
The invention provides a scheduling control method, device and system. The method comprises the following steps that after multiple controllers receive IO reading and writing requests, corresponding virtual volume types are determined according to types of the controllers, virtual volume type information is carried in the IO reading and writing requests, and the IO reading and writing requests are sent to corresponding IPO managers; the IPO managers schedule the IO reading and writing requests according to the virtual volume type information carried in the IO reading and writing requests, and target data are obtained. The burden of a caching device is relieved, and IO performance is improved.
Description
Technical field
The invention belongs to scheduling controlling field, particularly relate to a kind of dispatch control method, Apparatus and system.
Background technology
Figure 1 shows that the dispatch control method process flow diagram of prior art, comprise controller, buffer memory device, multiple disk unit (comprising: disk unit 1, disk unit 2 ... disk unit n); Wherein, described controller is connected with described multiple disk unit by described buffer memory device.
Described controller is sent to buffer memory device after receiving IO read-write requests; IO read-write requests is sent to corresponding disk unit by described buffer memory device, carries out reading and writing data process.
Figure 2 shows that the another dispatch control method process flow diagram of prior art, comprise multiple controller, buffer memory device, multiple disk unit; Wherein, described multiple controller is connected with described multiple disk unit by described buffer memory device;
Described multiple controller, after receiving IO read-write requests, sends IO read-write requests to described buffer memory device; IO read-write requests is sent to corresponding disk unit by described buffer memory device, carries out reading and writing data process, and described buffer memory device completes data syn-chronization between different controller by buffer memory mirror image simultaneously.
Because the data that user often uses mainly are put in buffer memory by buffer memory device, when user carries out IO read-write again, simplify read-write flow process thus shorten access time, if the scheduling of IO read-write requests is also come by buffer memory device, add buffer memory device burden so on the one hand, affect IO performance boost on the other hand.
Summary of the invention
The invention provides a kind of dispatch control method, Apparatus and system, to solve the problem.
The invention provides a kind of dispatch control method.Said method comprises the following steps:
After multiple controller receives IO read-write requests, determine corresponding virtual volume type according to controller type and virtual volume type information be carried in described IO read-write requests, described IO read-write requests being sent to corresponding IO manager;
Described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, obtains target data.
Present invention also offers a kind of dispatching control device, comprise receiver module, processing module, target data output module; Wherein, described receiver module is connected with described target data output module by described processing module;
Described receiver module, for receiving IO read-write requests and described IO read-write requests being sent to described processing module;
Described processing module, for determining corresponding virtual volume type according to controller type and being carried at by virtual volume type information in described IO read-write requests, is sent to described target data output module by described IO read-write requests;
Described target data output module, for according to the virtual volume type information carried in described IO read-write requests, dispatches described IO read-write requests, obtains target data.
Present invention also offers a kind of Dispatching Control System, comprise multiple controller, multiple IO manager, the communication server, buffer memory device, one or more disk unit; Wherein,
Master controller in described multiple controller is connected with buffer memory device by corresponding IO manager; Non-master controller in described multiple controller is connected with corresponding IO manager; Be connected by the communication server between described multiple IO manager; Described buffer memory device be connected with described one or more disk unit respectively;
Described multiple controller, after receiving IO read-write requests, determines corresponding virtual volume type according to controller type and is carried at by virtual volume type information in described IO read-write requests, described IO read-write requests being sent to corresponding IO manager;
Described IO manager, for according to the virtual volume type information carried in described IO read-write requests, carries out dispatch deal to described IO read-write requests.
By following scheme: after multiple controller receives IO read-write requests, determine corresponding virtual volume type according to controller type and virtual volume type information be carried in described IO read-write requests, described IO read-write requests being sent to corresponding IO manager; Described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, obtains target data; Reduce buffer memory device burden, improve IO performance.
By following scheme: described master controller sends described target data by IO manager, the communication server to the controller corresponding with non-master virtual volume after obtaining target data; Achieve data sharing.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Figure 1 shows that the dispatch control method process flow diagram of prior art;
Figure 2 shows that the another dispatch control method process flow diagram of prior art;
Figure 3 shows that the dispatch control method process flow diagram of the embodiment of the present invention 1;
Figure 4 shows that the dispatching control device structural drawing of the embodiment of the present invention 2;
Figure 5 shows that the Dispatching Control System structural drawing of the embodiment of the present invention 3.
Embodiment
Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.
Figure 3 shows that the dispatch control method process flow diagram of the embodiment of the present invention 1, comprise the following steps:
Step 301: multiple controller obtains main virtual volume, non-master virtual volume respectively;
Further, multiple controller obtains main virtual volume respectively, the process of non-master virtual volume is:
If multiple controller, then in described multiple controller, select a controller be master controller and set up main virtual volume in described master controller, in non-master controller, set up non-master virtual volume respectively;
By I/O management device and IO manager, the communication server between described multiple controller, broadcast main virtual volume, non-master virtual volume each other, obtain main virtual volume, non-master virtual volume respectively.
Further, multiple controller obtains main virtual volume respectively, the process of non-master virtual volume is: in multiple controller, set up main virtual volume, non-master virtual volume respectively.
Step 302: after multiple controller receives IO read-write requests, determines corresponding virtual volume type according to controller type and is carried in IO read-write requests by virtual volume type information, described IO read-write requests is sent to corresponding IO manager;
Further, described controller type comprises: master controller, non-master controller; Described virtual volume type comprises: main virtual volume, non-master virtual volume.
Wherein, controller type identifies corresponding with virtual volume type, virtual volume, as shown in table 1 below:
Controller type and virtual volume type, virtual volume identify the table of comparisons
| Controller type | Virtual volume type | Virtual volume identifies |
| Master controller | Main virtual volume | ID1 |
| Non-master controller 1 | Non-master virtual volume A | ID2 |
| Non-master controller 2 | Non-master virtual volume B | ID3 |
| … | … | … |
| Non-master controller n | Non-master virtual volume N | IDn |
Table 1
Step 303: described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, obtains target data.
Further, described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, and the process obtaining target data is:
If virtual volume type is main virtual volume, then described IO manager is dispatched described IO read-write requests, sends described IO read-write requests by buffer memory device to the disk unit of correspondence, obtains target data; Or,
Described IO manager sends described IO read-write requests to described buffer memory device, directly obtains target data.
Further, described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, and the process obtaining target data is:
If virtual volume type is non-master virtual volume, then described IO manager is dispatched described IO read-write requests, sends described IO read-write requests by the communication server to master controller;
After described master controller receives described IO read-write requests, send described IO read-write requests by the IO manager of correspondence to buffer memory device; Described buffer memory device sends described IO read-write requests to the disk unit of correspondence, obtains target data; Or,
After described master controller receives described IO read-write requests, send described IO read-write requests by the IO manager of correspondence to buffer memory device, directly obtain target data.
Further, described master controller sends described target data by the IO manager corresponding with master controller, the communication server to the IO manager that the controller corresponding with non-master virtual volume is corresponding after obtaining target data;
The IO manager that the controller corresponding with non-master virtual volume is corresponding sends described target data to the controller corresponding with non-master virtual volume.
Further, IO manager also comprises before dispatching described IO read-write requests:
Described IO manager creates the route thread of preset number and arranges corresponding scheduling queue according to type of service priority, and wherein, described preset number is equal with CPU number.
Further, the IO manager process of dispatching described IO read-write requests is as follows:
After described IO manager receives IO read-write requests, the service request type belonging to IO read-write requests, determines the scheduling queue of corresponding priority and described IO read-write requests is put into corresponding scheduling queue;
Described IO manager, according to scheduling queue priority, calls route thread, carries out dispatch deal to described IO read-write requests.
Further, described service request type comprises inquiry request, adds request, removal request.
Further, described IO manager storage service request type and the scheduling queue priority table of comparisons, as shown in table 2 below:
Service request type and the scheduling queue priority table of comparisons
| Service request type | Scheduling queue | Priority |
| Add request | Scheduling queue A | High |
| Inquiry request | Scheduling queue B | In |
| Removal request | Scheduling queue C | Low |
Table 2
Certainly, the concrete service request type listed in table 2 only illustrates, can also comprise other service request type (such as: Data Update request), is not used at this protection domain limiting the present embodiment.
Figure 4 shows that the dispatching control device structural drawing of the embodiment of the present invention 2, comprise receiver module 401, processing module 402, target data output module 403; Wherein, described receiver module 401 is connected with described target data output module 403 by described processing module 402;
Described receiver module 401, for receiving IO read-write requests and described IO read-write requests being sent to described processing module 402;
Described processing module 402, for determining corresponding virtual volume type according to controller type and being carried at by virtual volume type information in described IO read-write requests, is sent to described target data output module 403 by described IO read-write requests;
Described target data output module 403, for according to the virtual volume type information carried in described IO read-write requests, dispatches described IO read-write requests, obtains target data.
Figure 5 shows that the Dispatching Control System structural drawing of the embodiment of the present invention 3, comprise master controller; Non-master controller 1; IO manager 1; IO manager 2; The communication server; Buffer memory device; Disk unit 1, disk unit 2 ... disk unit n.
Master controller is connected with buffer memory device by IO manager 1; Non-master controller 1 is connected with IO manager 2; Described buffer memory device respectively with disk unit 1, disk unit 2 ... disk unit n is connected; Described IO manager 1 is connected with described IO manager 2 by the communication server;
If main virtual volume information is carried in described IO read-write requests and is sent to described IO manager 1 after receiving IO read-write requests by master controller;
Described IO manager 1 sends described IO read-write requests by buffer memory device to the disk unit of correspondence, obtains target data; Or,
Described IO manager 1 sends described IO read-write requests to described buffer memory device, directly obtains target data.
After if not master controller 1 receives IO read-write requests, non-master virtual volume information is carried in described IO read-write requests and is sent to IO manager 2;
Described IO manager 2 is dispatched described IO read-write requests, sends described IO read-write requests by the communication server, IO manager 1 to master controller;
After described master controller receives described IO read-write requests, send described IO read-write requests by IO manager 1 to buffer memory device; Described buffer memory device sends described IO read-write requests to the disk unit of correspondence, obtains target data; Or,
After described master controller receives described IO read-write requests, send described IO read-write requests by IO manager 1 to buffer memory device, directly obtain target data.
By following scheme: after multiple controller receives IO read-write requests, determine corresponding virtual volume type according to controller type and virtual volume type information be carried in described IO read-write requests, described IO read-write requests being sent to corresponding IO manager; Described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, obtains target data; Reduce buffer memory device burden, improve IO performance.
By following scheme: described master controller sends described target data by IO manager, the communication server to the controller corresponding with non-master virtual volume after obtaining target data; Achieve data sharing.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (10)
1. a dispatch control method, is characterized in that, comprises the following steps:
After multiple controller receives IO read-write requests, determine corresponding virtual volume type according to controller type and virtual volume type information be carried in described IO read-write requests, described IO read-write requests being sent to corresponding IO manager;
Described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, obtains target data.
2. method according to claim 1, is characterized in that, multiple controller also comprises before receiving IO read-write requests:
Multiple controller obtains main virtual volume, non-master virtual volume respectively.
3. method according to claim 2, is characterized in that, multiple controller obtains main virtual volume respectively, the process of non-master virtual volume is:
In described multiple controller, select a controller be master controller and set up main virtual volume in described master controller, in non-master controller, set up non-master virtual volume respectively;
By I/O management device and IO manager, the communication server between described multiple controller, broadcast main virtual volume, non-master virtual volume each other, obtain main virtual volume, non-master virtual volume respectively.
4. method according to claim 1, is characterized in that, described controller type comprises: master controller, non-master controller; Described virtual volume type comprises: main virtual volume, non-master virtual volume; Wherein, controller type identifies corresponding with virtual volume type, virtual volume.
5. method according to claim 1, is characterized in that, described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, and the process obtaining target data is:
If virtual volume type is main virtual volume, then described IO manager is dispatched described IO read-write requests, sends described IO read-write requests by buffer memory device to the disk unit of correspondence, obtains target data; Or,
Described IO manager sends described IO read-write requests to described buffer memory device, directly obtains target data.
6. method according to claim 1, is characterized in that, described IO manager, according to the virtual volume type information carried in described IO read-write requests, is dispatched described IO read-write requests, and the process obtaining target data is:
If virtual volume type is non-master virtual volume, then described IO manager is dispatched described IO read-write requests, sends described IO read-write requests by the communication server to master controller;
After described master controller receives described IO read-write requests, send described IO read-write requests by the IO manager of correspondence to buffer memory device; Described buffer memory device sends described IO read-write requests to the disk unit of correspondence, obtains target data; Or,
After described master controller receives described IO read-write requests, send described IO read-write requests by the IO manager of correspondence to buffer memory device, directly obtain target data.
7. method according to claim 6, is characterized in that, after described master controller obtains target data, sends described target data by the IO manager of correspondence, the communication server to the controller corresponding with non-master virtual volume.
8. the method according to claim 5 or 6, is characterized in that, the process that IO manager is dispatched described IO read-write requests is as follows:
After described IO manager receives IO read-write requests, the service request type belonging to IO read-write requests, determines the scheduling queue of corresponding priority and described IO read-write requests is put into corresponding scheduling queue;
Described IO manager, according to scheduling queue priority, calls route thread, carries out dispatch deal to described IO read-write requests.
9. a dispatching control device, is characterized in that, comprises receiver module, processing module, target data output module; Wherein, described receiver module is connected with described target data output module by described processing module;
Described receiver module, for receiving IO read-write requests and described IO read-write requests being sent to described processing module;
Described processing module, for determining corresponding virtual volume type according to controller type and being carried at by virtual volume type information in described IO read-write requests, is sent to described target data output module by described IO read-write requests;
Described target data output module, for according to the virtual volume type information carried in described IO read-write requests, dispatches described IO read-write requests, obtains target data.
10. a Dispatching Control System, is characterized in that, comprises multiple controller, multiple IO manager, the communication server, buffer memory device, one or more disk unit; Wherein,
Master controller in described multiple controller is connected with buffer memory device by corresponding IO manager; Non-master controller in described multiple controller is connected with corresponding IO manager; Be connected by the communication server between described multiple IO manager; Described buffer memory device be connected with described one or more disk unit respectively;
Described multiple controller, after receiving IO read-write requests, determines corresponding virtual volume type according to controller type and is carried at by virtual volume type information in described IO read-write requests, described IO read-write requests being sent to corresponding IO manager;
Described IO manager, for according to the virtual volume type information carried in described IO read-write requests, carries out dispatch deal to described IO read-write requests.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510583505.XA CN105183666B (en) | 2015-09-14 | 2015-09-14 | A kind of dispatch control method, apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510583505.XA CN105183666B (en) | 2015-09-14 | 2015-09-14 | A kind of dispatch control method, apparatus and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105183666A true CN105183666A (en) | 2015-12-23 |
| CN105183666B CN105183666B (en) | 2018-04-27 |
Family
ID=54905756
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510583505.XA Active CN105183666B (en) | 2015-09-14 | 2015-09-14 | A kind of dispatch control method, apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105183666B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776032A (en) * | 2016-12-22 | 2017-05-31 | 北京华云网际科技有限公司 | The treating method and apparatus of the I/O Request of distributed block storage |
| CN107728939A (en) * | 2017-09-26 | 2018-02-23 | 郑州云海信息技术有限公司 | I O scheduling method, apparatus, equipment and storage medium based on Linux |
| CN110674064A (en) * | 2019-09-05 | 2020-01-10 | 苏州浪潮智能科技有限公司 | Data transmission method, device, equipment and computer readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101291347A (en) * | 2008-06-06 | 2008-10-22 | 中国科学院计算技术研究所 | Network storage system |
| EP1736861B1 (en) * | 2005-06-02 | 2011-05-11 | Hitachi, Ltd. | A storage system for a storage pool and virtual volumes |
| CN104156216A (en) * | 2014-08-14 | 2014-11-19 | 浪潮(北京)电子信息产业有限公司 | Heterogeneous storage management system and method oriented to cloud computing |
-
2015
- 2015-09-14 CN CN201510583505.XA patent/CN105183666B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1736861B1 (en) * | 2005-06-02 | 2011-05-11 | Hitachi, Ltd. | A storage system for a storage pool and virtual volumes |
| CN101291347A (en) * | 2008-06-06 | 2008-10-22 | 中国科学院计算技术研究所 | Network storage system |
| CN104156216A (en) * | 2014-08-14 | 2014-11-19 | 浪潮(北京)电子信息产业有限公司 | Heterogeneous storage management system and method oriented to cloud computing |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776032A (en) * | 2016-12-22 | 2017-05-31 | 北京华云网际科技有限公司 | The treating method and apparatus of the I/O Request of distributed block storage |
| CN106776032B (en) * | 2016-12-22 | 2018-07-03 | 北京华云网际科技有限公司 | The treating method and apparatus of the I/O request of distributed block storage |
| CN107728939A (en) * | 2017-09-26 | 2018-02-23 | 郑州云海信息技术有限公司 | I O scheduling method, apparatus, equipment and storage medium based on Linux |
| CN110674064A (en) * | 2019-09-05 | 2020-01-10 | 苏州浪潮智能科技有限公司 | Data transmission method, device, equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105183666B (en) | 2018-04-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108848039B (en) | Server, message distribution method and storage medium | |
| CN102214117B (en) | Virtual machine management method, system and server | |
| WO2018149221A1 (en) | Device management method and network management system | |
| CN104954468A (en) | Resource allocation method and resource allocation device | |
| US20160330299A1 (en) | Data distribution method and system and data receiving apparatus | |
| CN113641457A (en) | Container creation method, device, apparatus, medium, and program product | |
| CN113419846B (en) | Resource allocation method and device, electronic equipment and computer readable storage medium | |
| US20180307509A1 (en) | Operating System for Distributed Enterprise Artificial Intelligence Programs on Data Centers and the Clouds | |
| US20170075836A1 (en) | Method and apparatus for automatic signal exchange between multiple embedded cpu boards | |
| CN104079614A (en) | Method and system for orderly obtaining messages of distributed publishing subscription system | |
| CN106406821A (en) | Data processing request sorting method and device | |
| CN105183666A (en) | Scheduling control method, device and system | |
| CN109902038B (en) | PCIe bus address space distribution method and device | |
| CN103685517A (en) | Storage hierarchical scheduling method and system based on service class characteristics | |
| CN106295927B (en) | Method and device for allocating tasks to operator | |
| WO2019044008A1 (en) | Distribution device and distribution method | |
| EP3208709A1 (en) | Batch processing method and device for system invocation commands | |
| TW202004492A (en) | Task management method, host and storage device for electronic storage device | |
| WO2021036319A1 (en) | Data cleaning method and system | |
| CN109213429B (en) | Storage management method and device | |
| CA3139693A1 (en) | Dynamic allocation of computing resources | |
| CN104410511B (en) | A kind of server management method and system | |
| CN102122268B (en) | Virtual machine memory allocation access method, device and system | |
| EP3667495A1 (en) | Task scheduling method, apparatus and device, and storage medium | |
| US20160139940A1 (en) | Systems and methods for creating virtual machine |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |