CN102426536B - Multitask data communication implementation method and system - Google Patents
Multitask data communication implementation method and system Download PDFInfo
- Publication number
- CN102426536B CN102426536B CN201110329140.XA CN201110329140A CN102426536B CN 102426536 B CN102426536 B CN 102426536B CN 201110329140 A CN201110329140 A CN 201110329140A CN 102426536 B CN102426536 B CN 102426536B
- Authority
- CN
- China
- Prior art keywords
- data
- client modules
- shared drive
- consumer
- distribution module
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a multitask data communication implementation method and system, and solves the problem that data exchange efficiency and data synchronization can not be implemented at the same time in Linux system when multiple tasks exchange mass data in the prior art. The method comprises steps as follows: a distribution module writes data acquired from a provider into a shared internal memory according to registered data types of client modules as consumers and client characteristic information; the distribution module informs the client modules as consumers to read the data in the shared internal memory according to the registered data types and client characteristic information, wherein the client modules do not influence each other when reading the data, thereby maximizing the data exchange efficiency; and the distribution module can inform the client module of data loss and lost data volume when any client module does not process data in time and lose data. The invention is applicable to data communication in Linux system.
Description
Technical field
The present invention relates to data communication field, relate in particular to implementation method and the system of data communication between a kind of multitask.
Background technology
In the application of embedded system, tending to run into has a large amount of real time datas need to deliver to the situation that distinct program is processed by different clients, now also require each treatment progress in Data dissemination process when desired data is lost, can be notified and know lost data bulk.But, higher, limited with respect to the embedded system internal memory of speed that these data itself conventionally produce, the memory headroom taking is comparatively considerable, and mass data when exchange between process, conventionally adopts efficient shared drive mechanism.
But, when the above-mentioned shared drive mechanism of application, inventor finds that in prior art, at least there are the following problems: when shared drive is accessed in a plurality of processes simultaneously, lack synchronization mechanism, easily cause the disorder of sharing data, make in shared drive data no longer consistent with source data.Meanwhile, shared drive adopts unformatted data, is not easy to the processing of data.
Summary of the invention
Embodiments of the invention provide implementation method and the system of data communication between a kind of multitask, to improve the data-handling efficiency in linux system.
For achieving the above object, embodiments of the invention adopt following technical scheme:
An implementation method for data communication between multitask, comprising:
Distribution module obtains data from data source;
Distribution module is written to shared drive according to the registered data type of each client modules and client feature information as consumer by described data;
Described distribution module notifies described each client modules as consumer to read the data in described shared drive according to described registered data type and client feature information.
Further, said method also can also comprise:
Described distribution module, when task start, is linked on the shared drive that is used to described each client modules storage data as consumer having created; To data type and the characteristic information of data structure registration oneself, wherein, described characteristic information at least comprises that distribution module ID and data write the writing mode of shared drive; According to distribution module ID, create the message queue corresponding with self, and create and each client modules message queue one to one according to each client modules ID; Establishment is used to indicate the operable lock writing;
Described each client modules as consumer, when its task start, is linked on the shared drive that is used to its storage data having created; To data structure registration, be used to indicate distribution module notice and as consumer's client modules, read information and the client feature information of the data in described shared drive, wherein, client feature information at least comprises described client modules ID and the reading manner of reading out data from shared drive; Each client modules as consumer all creates the message queue corresponding with distribution module according to distribution module ID, and create the message queue corresponding with self according to the client modules ID of self, and create and other client modules message queue one to one according to other client modules ID; Described in establishment, be used to indicate the operable lock reading.
Further, the method also can comprise:
Described distribution module, before said write, is designated as the described operable lock writing that is used to indicate to write lock, and representative does not receive other access in the process that writes described shared drive;
Described distribution module is being notified after described each client modules as consumer reads the data in described shared drive, and the described operable lock writing that is used to indicate is designated as to solution and writes lock.
Correspondingly, the method also can comprise:
For described in each as consumer's client modules, after receiving the described notice of described distribution module, the described operable lock reading that is used to indicate is designated as to read lock, representative allows read access in reading the process of described shared drive, but refusal write access, and start to read the data in described shared drive;
Described in each, as consumer's client modules, after the data in having read described shared drive, the described operable lock reading that is used to indicate is designated as to solution read lock.
Wherein, the described data that start to read in described shared drive are specially: described in each, as consumer's client modules, the reading manner during according to registration starts to read the data in described shared drive, described reading manner comprises: first write first reading manner, after write first reading manner, and the mode that simultaneously reads a plurality of data.
Especially, the method also comprises:
Described in each, as consumer's client modules, after the data at every turn having read described shared drive, by putting the mode of a flag in described shared drive, notify described distribution module whether to continue to send to the message queue of described each client modules as consumer the notice that reads shared drive.
The system that realizes of data communication between multitask, comprising: distribution module, and at least one client modules; Wherein, described at least one client modules at least can become the client modules as consumer;
Described distribution module, for being written to shared drive according to the registered data type of the described client modules as consumer and client feature information by described data; And notify the described client modules as consumer to read the data in described shared drive according to described registered data type and client feature information;
The described client modules as consumer, for after receiving described notice, starts to read the data in described shared drive.
Further, described distribution module, also for when the task start, is linked on the shared drive that is used to described each client modules storage data as consumer having created; To data type and the characteristic information of data structure registration oneself, wherein, described characteristic information at least comprises that distribution module ID and data write the writing mode of shared drive; According to distribution module ID, create the message queue corresponding with self, and create and each client modules message queue one to one according to each client modules ID; Establishment is used to indicate the operable lock writing;
Described in each, as consumer's client modules, also, for when the task start separately, be linked on the shared drive that is used to its storage data having created; To data structure registration, be used to indicate distribution module notice and as consumer's client modules, read information and the client feature information of the data in described shared drive, wherein, client feature information at least comprises described client modules ID and the reading manner of reading out data from shared drive; Each client modules as consumer all creates the message queue corresponding with distribution module according to distribution module ID, and create the message queue corresponding with self according to the client modules ID of self, and create and other client modules message queue one to one according to other client modules ID; Described in establishment, be used to indicate the operable lock reading.
Further, described distribution module, also for before said write, is designated as the described operable lock writing that is used to indicate to write lock, and representative does not receive other access in the process that writes described shared drive; And notifying after the described client modules as consumer reads the data in described shared drive, the described operable lock writing that is used to indicate is designated as to solution and writes lock;
Described in each as consumer's client modules, also for after receiving the described notice of described distribution module, the described operable lock reading that is used to indicate is designated as to read lock, representative allows read access in reading the process of described shared drive, but refusal write access, and start to read the data in shared drive; After data in having read described shared drive, the described operable lock reading that is used to indicate is designated as to solution read lock;
Wherein, the described data that start to read in described shared drive are specially: described in each, as consumer's client modules, the reading manner during according to registration reads the data in described shared drive, described reading manner comprises: first write first reading manner, after write first reading manner, and the mode that simultaneously reads a plurality of data.
Especially, described in each as consumer's client modules, also for after having read the data of described shared drive at every turn, by putting the mode of a flag in described shared drive, notify described distribution module whether to the message queue of described each client modules as consumer, to send the notice that reads shared drive.
The such scheme that the present embodiment provides, the data type that the task process of each client modules needs by registration, in the process of operation, obtain the data of registration type, therefore, when client modules does not need data, distribution module is no longer distributed data, and then economizes on resources, and has improved the efficiency of exchanges data.Meanwhile, for the module that only needs reading out data, by reading with other client modules is concurrent when the read data, improved the efficiency of shared drive exchanges data.By the read lock in data exchange process, write lock control, accomplished the data protection between a plurality of tasks, complete data synchronous, and taken into account exchanges data efficiency.In addition, during described each client modules reading out data, be independent of each other, maximizing exchanges data efficiency; Described distribution module, when each client modules has data do not process in time and lose, can notify this client modules to have loss of data, and the data bulk of simultaneously notifying this client to lose.
Accompanying drawing explanation
Fig. 1 is related to schematic diagram between each client modules in the embodiment of the present invention one;
Fig. 2 is the schematic flow sheet of the implementation method of data communication between the multitask in the embodiment of the present invention one;
Fig. 3 is the schematic diagram of the system of the implementation method of data communication between the multitask in the embodiment of the present invention two.
Embodiment
Embodiment mono-:
The present embodiment provides the implementation method of data communication between a kind of multitask, is applicable to the data communication under linux system.As shown in Figure 1, in the method, distribution module obtains data from data source, Data dissemination mainly carries out round Yi Ge shared drive district, as each client modules of the user of data source, as the operation of the task of consumer's client modules to carry out the center that is exchanged for of data with shared memory field.In the present invention, each client modules both can be the supplier of a plurality of data types simultaneously, also can be the consumer of a plurality of data types simultaneously, or be supplier and the consumer of a plurality of data types simultaneously, and can change at any time during the course the role of oneself, therefore in the present embodiment as supplier's client modules and for consumer's client modules be can be same client modules.
In the method, first need distribution module when task start (as powering on), carry out operation as follows:
Being linked to being used to as each client modules of consumer of having created stores on the shared drive of data;
To data type and the characteristic information of data structure registration oneself, wherein, this data type can be for example type of waveform, real-time type etc.; For example: the data type of distribution module has waveform and in real time (for example voltage, electric current etc.); This characteristic information at least comprises that distribution module ID and distribution module write the writing mode in shared drive by data;
According to distribution module ID, create the message queue corresponding with self, and create and each client modules message queue one to one according to each client modules ID; For example, distribution module A, client modules B, client modules C carries out data communication, and distribution module can be respectively according to distribution module ID (A) when creating message queue, client modules ID (B), client modules ID (C), create message queue msg (A), msg (B), msg (C).
Establishment is used to indicate the operable lock writing.
Similarly, each client modules as consumer, when its task start, is also carried out following corresponding operation:
Be linked on the shared drive that is used to its storage data having created;
To data structure registration, be used to indicate distribution module notice and as consumer's client modules, read information and the client feature information of data in shared drive, wherein, client feature information at least comprises described client modules ID and the reading manner of reading out data from shared drive, this reading manner can comprise and first writes first reading manner, and after write first reading manner, and and support to read the mode of a plurality of data simultaneously;
Each client modules as consumer all creates the message queue corresponding with distribution module according to distribution module ID, and create the message queue corresponding with self according to the client modules ID of the described client modules as consumer of self, and create and other client modules message queue one to one according to other client modules ID; For example, for above-mentioned distribution module A, client modules B, client modules C carries out the embodiment of data communication, client modules B is respectively according to distribution module ID (A), client modules ID (B), client modules ID (C) create message queue msg (A), msg (B), msg (C); Equally, client modules C is also respectively according to distribution module ID (A), and client modules ID (B), client modules ID (C) create such message queue msg (A), msg (B), msg (C).Wherein, the message queue corresponding with self that distribution module creates and the establishment of each client modules with the corresponding message queue of distribution module be same message queue; In like manner, the message queue corresponding with arbitrary client modules that distribution module creates and the establishment of each client modules with the corresponding message queue of this arbitrary client modules be same message queue.
Described in establishment, be used to indicate the operable lock reading.
At distribution module and each client modules, all complete after said process, as described in Figure 2, the communication process while executing the task between concrete distribution module and each client modules as consumer is as follows, comprising:
Step 101, distribution module is from being for example that the data source of DSP is obtained data;
Step 102, distribution module is designated as the operable lock that is used to indicate write operation creating to write lock, and representative does not receive other access in the process that writes described shared drive;
For example: distribution module can be realized and be write lock by signal lamp mechanism, and representative will be carried out the operation that writes shared drive, not allow other client modules to conduct interviews to shared drive in this operating process.
Step 103, distribution module is written to above-mentioned data in shared drive according to the registered data type of each client modules and client feature information;
Particularly, take client modules 1 as example, distribution module is after being linked to shared drive, according to the data type of client modules 1 registration (type of waveform and in real time type), in shared drive, marked off corresponding buffer, and each buffer is respectively used to the message queue of corresponding type of waveform or real-time type.
Distribution module is according to the type of waveform of client modules 1 registration as consumer and real-time type, and the client modules ID of client modules 1, the data that belong to the type of waveform of client modules 1 in the data of obtaining are written in buffer corresponding in shared drive, the data that belong to the real-time type of client modules 1 in the data of obtaining are written to buffer corresponding in shared drive.
Step 104, distribution module reads the data in described shared drive according to described registered data type and described each client modules of client feature information notice.
For example: distribution module reads in shared drive the data of type of waveform according to the ID notice client modules 1 of client modules 1.
Step 105, after notice reads the data in described shared drive as each client modules of consumer, distribution module is designated as solution by described operable lock and writes lock.
This step 105, with above-mentioned 102 corresponding, can be designated as solution by realizations such as signals equally and write lock, represents that shared drive write operation finishes, and can receive other access as consumer's client modules etc.
Below, take a client modules as consumer as example,
Step 106, after the notice as client modules distribution module in receiving step 104 of consumer, is designated as read lock by being used to indicate the operable lock reading, and representative allows read access in reading the process of described shared drive, but refusal write access;
Step 107, starts to read the data in shared drive as consumer's client modules;
Particularly, as consumer's client modules reading manner as required, start to read the data in shared drive, described reading manner comprises: first write first reading manner, read in order the data in message queue, after write first reading manner, read the data of up-to-date storage in shared drive, and the mode that simultaneously reads a plurality of data.If the interface function here reading in order as consumer's client call, the client modules as consumer will sequentially read the data in shared drive; If read the interface function of latest data as consumer's client call, the client modules as consumer will read latest data.
In addition, in the present embodiment, whether each client modules as consumer is reading after the data in corresponding shared drive at every turn, can notify described distribution module to continue to send to the message queue of described each client modules as consumer the notice that reads shared drive by putting the mode of a flag in shared drive.Thus in home position in: during the state that no longer continues to read, distribution module just can not write data after shared drive, sends the notification to this client modules as consumer, and then can save system resource.
Step 108, after the data as consumer's client modules in having read shared drive, is designated as solution read lock by described operable lock.Now, other client modules can be accessed shared drive.
In the method that the present embodiment provides, after getting up-to-date data, upgrades distribution module the data of shared drive, according to the data type of each client modules registration as consumer, write the message queue corresponding with each client modules, each client modules passes through processing messages queue real-time update data in the process of operation.And, as each client modules of consumer when obtaining the data of message queue, can automatically read latest data according to the reading manner in when registration, and then reduced between process exchanges data frequently, treatment effeciency to the data in shared drive in linux system is provided, and has saved system resource.
Embodiment bis-:
The present embodiment provides the system that realizes of data communication between a kind of multitask, as shown in Figure 3, comprising: shared drive 30, especially, also comprise distribution module 31, and at least one client modules 32; This at least one client end module 32 can be the client modules as supplier, can be also the client modules as consumer.
Distribution module 31, for being written to shared drive 30 according to the registered data type of client modules 32 and client feature information as consumer by described data; And notify the client modules 32 as consumer to read the data in described shared drive 30 according to described registered data type and client feature information;
Each for after receiving notice, starts to read the data in shared drive 30 as consumer's client modules 32.
In addition, in the present embodiment, distribution module 31, also for when the task start, is linked to and creates on the shared drive 30 being used to as consumer's client modules 32 storage data; Register oneself data type and characteristic information, wherein, described characteristic information at least comprises distribution module ID and to writing mode during data writing in shared drive; According to distribution module ID, create the message queue corresponding with self, and create and each client modules message queue one to one according to each client modules ID; Establishment is used to indicate the operable lock writing;
Described in each, as consumer's client modules 32, also, for when the task start separately, be linked to the shared drive 30 that is used to its storage data having created; Each client modules as consumer all creates the message queue corresponding with distribution module according to distribution module ID, and create the message queue corresponding with self according to the client modules ID of self, and create and other client modules message queue one to one according to other client modules ID; Described in establishment, be used to indicate the operable lock reading.
Further, distribution module 31, also for before writing, is designated as and writes lock being used to indicate the operable lock writing, and representative does not receive other access in the process that writes shared drive 30; And after notice reads the data in shared drive 30 as each client modules 32 of consumer, by being used to indicate the operable lock writing, being designated as solution and writing lock;
Each is as consumer's client modules 32, also, for after receiving the notice of distribution module 31, by being used to indicate the operable lock reading, be designated as read lock, representative allows read access in the process that reads shared drive 30, but refusal write access, and start to read the data in shared drive; After data in having read shared drive, by being used to indicate the operable lock reading, be designated as solution read lock;
Wherein, the data that start to read in shared drive are specially: each client modules 32 as consumer calls corresponding reading manner interface function as required, and reading manner comprises: first write first reading manner, and after write first reading manner.
Further, in the present embodiment, each is as consumer's client modules 32, also for after having read the data of shared drive at every turn, by putting the mode of a flag in shared drive 30, notify distribution module 31 whether to the message queue of described each client modules 32 as consumer, to send the notice that reads shared drive.
In another system embodiment of the present invention, this system has been applied to power quality analyzer ARZ-3W, ARZ-3M, in ARZ-3B system, therefore can be distributed to a large amount of power quality datas in demonstration, record, monitoring and host computer service role and go.
The system that the present embodiment provides is because distribution module can be according to data type data writing, client modules can read as required, so can directly carry out the process exchange of reading out data, therefore avoided the technical matters of the frequent exchange that repeatedly causes alternately, and at each client modules as consumer no longer in reading out data, distribution module just can no longer send notice to each client modules as consumer according to zone bit, so obtained, save system resource, improved the technique effect of exchanges data efficiency.
The above; be only the specific embodiment of the present invention, but protection scope of the present invention is not limited to this, is anyly familiar with those skilled in the art in the technical scope that the present invention discloses; can expect easily changing or replacing, within all should being encompassed in protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion by the described protection domain with claim.
Claims (8)
1. an implementation method for data communication between multitask, is characterized in that, comprising:
Distribution module obtains data from data source;
Distribution module is written to shared drive according to the registered data type of each client modules and client feature information as consumer by described data;
Described distribution module notifies described each client modules as consumer to read the data in described shared drive according to described registered data type and client feature information;
Described implementation method also comprises:
Described distribution module, when task start, is linked on the shared drive that is used to described each client modules storage data as consumer having created; To data type and the characteristic information of data structure registration oneself, wherein, described characteristic information at least comprises that distribution module ID and data write the writing mode of shared drive; According to distribution module ID, create the message queue corresponding with self, and create and each client modules message queue one to one according to each client modules ID; Establishment is used to indicate the operable lock writing;
Described each client modules as consumer, when its task start, is linked on the shared drive that is used to its storage data having created; To data structure registration, be used to indicate distribution module notice and as each client modules of consumer, read information and the client feature information of the data in described shared drive, wherein, client feature information at least comprises described client modules ID and the reading manner of reading out data from shared drive; Each client modules as consumer all creates the message queue corresponding with distribution module according to distribution module ID, and create the message queue corresponding with self according to the client modules ID of self, and create and other client modules message queue one to one according to other client modules ID; Establishment is used to indicate the operable lock reading.
2. the implementation method of data communication between multitask according to claim 1, is characterized in that, the method also comprises:
Described distribution module, before said write, is designated as the described operable lock writing that is used to indicate to write lock, and representative does not receive other access in the process that writes described shared drive;
Described distribution module is being notified after described each client modules as consumer reads the data in described shared drive, and the described operable lock writing that is used to indicate is designated as to solution and writes lock.
3. the implementation method of data communication between multitask according to claim 2, is characterized in that, the method also comprises:
For described each client modules as consumer, after receiving the described notice of described distribution module, the described operable lock reading that is used to indicate is designated as to read lock, representative allows read access in reading the process of described shared drive, but refusal write access, and start to read the data in described shared drive;
Described each client modules as consumer, after the data in having read described shared drive, is designated as solution read lock by the described operable lock reading that is used to indicate.
4. the implementation method of data communication between multitask according to claim 3, it is characterized in that, the described data that start to read in described shared drive are specially: described each client modules as consumer reading manner as required starts to read the data in described shared drive, described reading manner comprises: first write first reading manner, after write first reading manner, and the mode that simultaneously reads a plurality of data.
5. according to the implementation method of data communication between the multitask described in claim 3 or 4, it is characterized in that, the method also comprises:
After the data of described each client modules as consumer at every turn having read described shared drive, by putting the mode of a flag in described shared drive, notify described distribution module whether to continue to send to the message queue of described each client modules as consumer the notice that reads shared drive.
6. the system that realizes of data communication between multitask, is characterized in that, comprising: distribution module and at least one client modules; Wherein, described at least one client modules at least can become each client modules as consumer;
Described distribution module, for being written to shared drive according to the described registered data type of each client modules and client feature information as consumer by described data; And notify described each client modules as consumer to read the data in described shared drive according to described registered data type and client feature information;
Described each client modules as consumer, for after receiving described notice, starts to read the data in described shared drive;
Described distribution module, also for when the task start, is linked on the shared drive that is used to described each client modules storage data as consumer having created; To data type and the characteristic information of data structure registration oneself, wherein, described characteristic information at least comprises that distribution module ID and data write the writing mode of shared drive; According to distribution module ID, create the message queue corresponding with self, and create and each client modules message queue one to one according to each client modules ID; Establishment is used to indicate the operable lock writing;
Described each client modules as consumer, also for when the task start separately, is linked on the shared drive that is used to its storage data having created; To data structure registration, be used to indicate distribution module notice and as each client modules of consumer, read information and the client feature information of the data in described shared drive, wherein, client feature information at least comprises described client modules ID and the reading manner of reading out data from shared drive; Each client modules as consumer all creates the message queue corresponding with distribution module according to distribution module ID, and create the message queue corresponding with self according to the client modules ID of self, and create and other client modules message queue one to one according to other client modules ID; Establishment is used to indicate the operable lock reading.
7. the system that realizes of data communication between multitask according to claim 6, is characterized in that,
Described distribution module, also for before said write, is designated as the described operable lock writing that is used to indicate to write lock, and representative does not receive other access in the process that writes described shared drive; And notifying after described each client modules as consumer reads the data in described shared drive, the described operable lock writing that is used to indicate is designated as to solution and writes lock;
Described each client modules as consumer, also for after receiving the described notice of described distribution module, the described operable lock reading that is used to indicate is designated as to read lock, representative allows read access in reading the process of described shared drive, but refusal write access, and start to read the data in shared drive; After data in having read described shared drive, the described operable lock reading that is used to indicate is designated as to solution read lock;
Wherein, the described data that start to read in described shared drive are specially: described each client modules as consumer reading manner as required reads the data in described shared drive, described reading manner comprises: first write first reading manner, after write first reading manner, and the mode that simultaneously reads a plurality of data.
8. the system that realizes of data communication between multitask according to claim 7, it is characterized in that, described each client modules as consumer, also for after having read the data of described shared drive at every turn, by putting the mode of a flag in described shared drive, notify described distribution module whether to the message queue of described each client modules as consumer, to send the notice that reads shared drive.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110329140.XA CN102426536B (en) | 2011-10-26 | 2011-10-26 | Multitask data communication implementation method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110329140.XA CN102426536B (en) | 2011-10-26 | 2011-10-26 | Multitask data communication implementation method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102426536A CN102426536A (en) | 2012-04-25 |
| CN102426536B true CN102426536B (en) | 2014-04-09 |
Family
ID=45960525
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110329140.XA Expired - Fee Related CN102426536B (en) | 2011-10-26 | 2011-10-26 | Multitask data communication implementation method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102426536B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103634707A (en) * | 2012-08-23 | 2014-03-12 | 上海斐讯数据通信技术有限公司 | Communication method |
| CN104850551B (en) * | 2014-02-13 | 2020-02-28 | 腾讯科技（深圳）有限公司 | Data processing method and device and mobile terminal |
| CN105700962A (en) * | 2014-11-26 | 2016-06-22 | 中兴通讯股份有限公司 | Data update processing method and apparatus |
| CN104834572B (en) * | 2015-05-12 | 2019-02-15 | 四川九洲空管科技有限责任公司 | Data communications method in synthesization airborne collision avoidance system between each independent particle system |
| CN105278922A (en) * | 2015-09-29 | 2016-01-27 | 新浪网技术(中国)有限公司 | Data distribution method, system and apparatus |
| CN106506703B (en) * | 2016-12-28 | 2018-06-08 | 掌阅科技股份有限公司 | Service discovery method, apparatus and system, server based on shared drive |
| CN107085542B (en) * | 2017-05-05 | 2020-03-31 | 深圳慧昱教育科技有限公司 | IPC communication method and server |
| CN107391278A (en) * | 2017-07-25 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of front and back end communication means based on shared drive |
| CN107491355A (en) * | 2017-08-17 | 2017-12-19 | 山东浪潮商用系统有限公司 | Funcall method and device between a kind of process based on shared drive |
| CN108833477B (en) * | 2018-05-16 | 2020-09-29 | 百度在线网络技术（北京）有限公司 | Message transmission method, system and device based on shared memory |
| CN109089301B (en) * | 2018-07-19 | 2021-01-15 | 深圳云盈网络科技有限公司 | Network data processing system and method |
| CN111026561B (en) * | 2019-10-30 | 2022-11-08 | 烽火通信科技股份有限公司 | Data communication method and system of cloud platform and computer readable medium |
| CN111338583B (en) * | 2020-05-19 | 2020-08-25 | 北京数字绿土科技有限公司 | High-frequency data storage method and device and computer |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1197955A (en) * | 1997-04-17 | 1998-11-04 | 阿尔卡塔尔-阿尔斯托姆通用电气公司 | Method of managing shared memory |
| CN101847105A (en) * | 2009-03-26 | 2010-09-29 | 联想(北京)有限公司 | Computer and internal memory sharing method of a plurality of operation systems |
| WO2011023617A1 (en) * | 2009-08-25 | 2011-03-03 | International Business Machines Corporation | Cache partitioning in virtualized environments |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8312227B2 (en) * | 2007-05-31 | 2012-11-13 | Intel Corporation | Method and apparatus for MPI program optimization |
-
2011
- 2011-10-26 CN CN201110329140.XA patent/CN102426536B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1197955A (en) * | 1997-04-17 | 1998-11-04 | 阿尔卡塔尔-阿尔斯托姆通用电气公司 | Method of managing shared memory |
| CN101847105A (en) * | 2009-03-26 | 2010-09-29 | 联想(北京)有限公司 | Computer and internal memory sharing method of a plurality of operation systems |
| WO2011023617A1 (en) * | 2009-08-25 | 2011-03-03 | International Business Machines Corporation | Cache partitioning in virtualized environments |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102426536A (en) | 2012-04-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102426536B (en) | Multitask data communication implementation method and system | |
| CN102713854B (en) | Method and apparatus for saving and restoring container state | |
| CN102752093B (en) | Based on the data processing method of distributed file system, equipment and system | |
| CN104268025A (en) | Interprocess communication method and system, and server | |
| EP2717533A1 (en) | Method, network card and hard disk card for accessing to shut-down hard disk | |
| CN102571850A (en) | Transaction committing system, method and equipment | |
| WO2023143503A1 (en) | Resource scheduling system and method | |
| CN103049527A (en) | Large power grid oriented parallel real-time database master and slave switching management system | |
| CN103634126A (en) | Multicast information transmission method and device | |
| CN111078238A (en) | Centralized processing method and device for application configuration in container environment | |
| CN102520982A (en) | Method and device of node hot plug | |
| US8948091B2 (en) | Push management scheme | |
| US8417222B1 (en) | Systems and methods for delivering messages based on a device radio status | |
| CN104022842A (en) | Multicast information transmission method and device | |
| CN104750545A (en) | Process scheduling method and device | |
| CN102103530B (en) | Snapshot methods, snapshot device and snapshot system | |
| CN103164223A (en) | Method of intelligent terminal capable of achieving alarm clock and intelligent terminal under shutdown state | |
| CN110661869B (en) | Node online method, system, device, equipment and computer storage medium | |
| CN106851535B (en) | Method and device for sharing Bluetooth by multiple systems | |
| CN103677200A (en) | Computer system and power management method | |
| CN115454666A (en) | Data synchronization method and device among message queue clusters | |
| CN103593305A (en) | Information processing apparatus, information processing method, and program | |
| CN113709202B (en) | Method and system for waking up system chip | |
| CN104580328A (en) | Virtual machine migration method, device and system | |
| CN113918436A (en) | Log processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20140409 Termination date: 20151026 |
|
| EXPY | Termination of patent right or utility model |