CN110196777A - The method that real-time Binder processing in real-time Android operation system avoids non real-time Binder competition - Google Patents
The method that real-time Binder processing in real-time Android operation system avoids non real-time Binder competition Download PDFInfo
- Publication number
- CN110196777A CN110196777A CN201910356823.0A CN201910356823A CN110196777A CN 110196777 A CN110196777 A CN 110196777A CN 201910356823 A CN201910356823 A CN 201910356823A CN 110196777 A CN110196777 A CN 110196777A
- Authority
- CN
- China
- Prior art keywords
- binder
- real
- time
- request
- common
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses the methods that the real-time Binder processing in real-time Android operation system avoids non real-time Binder competition, it is characterized in that, the following steps are included: s1: determining the property of Binder request, belong to real-time Binder request or common Binder request, if Binder request in real time thens follow the steps S2；S2:Binder drives to IPCThreadState class example request thread, and when SPAWN goes out strong or soft real-time thread for handling real-time Binder to request;S3:Binder driving, which is impartial to, all real-time Binde or requests real-time Binder in orderly insertion queue.
Description
Technical field
The present invention relates to technical field of communication processing, and in particular to real-time in a kind of real-time Android operation system
The method that Binder processing avoids non real-time Binder competition.
Background technique
With SOC(System On Chip) continuous development of technology, embedded system produces in people, life it is each
Aspect arrive greatly space flight and aviation using more and more extensive, small to arrive smart phone, smartwatch etc., it may be said that be ubiquitous.Due to
The particularity of work, many embedded devices require the response of system external portion event must be within the time limit for realizing setting
It completes, makes system that there is predictability, therefore must just use real time operating system.
VxWorks when common embedded real-time operating system includes hard, QNX and uCOSII etc. are soft then to include in real time
There is WinCE etc..As VxWorks, QNX and uCOSII etc. are the fairly simple closed operating systems of some functions.With existing
System it is increasingly sophisticated, have increasing need for the time sharing operating system for some general having being improved ecological chain, such as: Linux,
Windows etc. is transformed into real time operating system, had not only been able to satisfy general requirment in this way but also had been able to satisfy specific demand.Since Linux is opened
The characteristic in source, this respect have some good solutions, such as: RTLinux, RTAI, MontaVista.
It the use of more and more extensive Google's Android (Android) operating system is also that ecology is improved in general the having of one kind now
The time sharing operating system of chain, it is based on linux kernel.Most important Inter-Process Communication machine in Android (Android) operating system
System is exactly Binder mechanism.Binder mechanism can be described as ubiquitous in Android (Android) operating system.Common
Binder mechanism is used to handle non real-time logic, also without the concept of introducing priority.Real-time Android operation system
(RTAndroid) Binder mechanism can be used to handle Real-time Logic in.But it is used for Binder mechanism to handle Real-time Logic
There is one to have to solve the problems, such as, since Binder mechanism can be described as nowhere not in Android (Android) operating system
In same process, when handling non real-time Binder request, since the todo chained list in Binder driving has added lock, only
Have after non real-time Binder request has been handled, real-time Binder can just be handled, this is obviously and the design of real-time system is former
Then misfit.Specifically, existing Binder communication mechanism is after consumer process initiates Binder request, to arrive first
Class and interface class are serviced up to Binder, then reaches Binder core classes, then reaches IPCThreadState class, finally arrives at fortune
Row drives in the Binder of kernel spacing.The result of request returns to consumer process by opposite route.IPCThreadState
Class is responsible for and Binder driving communicates and maintains Binder thread pool.In the present design of Android, in each consumer process
All examples of only one IPCThreadState class.In addition, there are one special Binder to service for Android system
ServiceManager, it provides name Service for Binder mechanism.Binder is driven to each process and maintains binder_
The data structure of proc, and on binder_proc also include waiting list, such binder thread can sleep above.In addition,
Also fifo queue is maintained on binder_proc, to cache binder driving all untreated work in some process.Separately
Outside, binder driving also maintains lock, to synchronize binder request concurrent in the same process.
In real-time Android operation system (RTAndroid), Binder mechanism is also used to handle real-time event or ask
The striding course transmitting demand asked, because Binder mechanism is a kind of efficient and flexible in programming striding course communication mechanism.From above
Analysis can be with if do not improved the Binder mechanism of Android primary, the Binder processing of real-time event or request does not have
It is distinguished and treats, when the non real-time Binder request in system is frequent and busy, at the Binder of real-time event or request
Reason will postpone very much, and real-time performance will cannot be guaranteed.
Summary of the invention
It is an object of that present invention to provide the real-time Binder processing in real-time Android operation system to avoid non real-time Binder
The method of competition is realized based on real-time Android operation system, is operated suitable for Android operation system is transformed into real-time Android
In system, be also applied in any real time operating system using Binder mechanism, come avoid real-time Binder handle when, non-reality
When Binder request race problem.
To achieve the goals above, the invention adopts the following technical scheme:
The method that real-time Binder processing in real-time Android operation system avoids non real-time Binder competition, which is characterized in that
The following steps are included:
S1: determining the property of Binder request, belongs to real-time Binder request or common Binder request, if in real time
Binder request thens follow the steps S2；
S2:Binder drives to IPCThreadState class example request thread, when SPAWN goes out strong or soft real-time thread with
For handling real-time Binder request;
S3:Binder driving, which is impartial to, all real-time Binde or requests real-time Binder in orderly insertion queue.
As a kind of optimal technical scheme, including being located away from the mode of common Binder mechanism and/or being embedded in common
The mode of Binder；
The mode for being located away from common Binder mechanism refers to that there are two Binder driving and corresponding device files in system, respectively
For primary Binder driving and real-time Binder driving；One consumer process there are the example of two IPCThreadState classes,
The example of the example of common IPCThreadState class and real-time IPCThreadState class respectively, for its operation include with
Lower step:
S1a: the Binder service class and interface class and Binder core classes on upper layer can distinguish Binder request property,
If real-time IPCThreadState class example is then found in Binder request in real time, if common Binder request then find it is general
Logical IPCThreadState class example；
S2a: real-time Binder request sends the requests to real-time Binder by real-time IPCThreadState class example and drives
It is dynamic；When the real-time real-time IPCThreadState class example SPAWN of Binder driving request goes out strong or soft real-time thread with
It is requested in handling real-time Binder；
S3a: real-time Binder drives all real-time Binder that are impartial to request or according to priority they are inserted into an orderly manner
Into the fifo queue of corresponding one or more processes；
Be embedded in the mode of common Binder, only deposit Binder driving in system, each consumer process also only one
The example of IPCThreadState class has in the library Binder specific to the real-time Binder interface requested or the additional ginseng of interface
Number is real-time Binder request or common Binder request to distinguish, and operation includes following procedure:
S1b: by the library Binder particular interface or interface parameters indicate that Binder request is a real-time Binder request；
When S2b:Binder drives to IPCThreadState class example request SPAWN thread, by special parameter or
It is specifically ordered in Binder agreement, when the thread for indicating that needs create is strong or soft real-time thread, IPCThreadState
Class example will create corresponding thread to handle real-time Binder request in such thread；
Sb3: it in the corresponding binder_proc structure of each consumer process, is specially maintained in real time for real-time Binder request
The fifo queue rt_todo_list of the waiting list rt_wait_queue and real-time Binder of Binder.
As a kind of optimal technical scheme, when system configures above two mode simultaneously, software transfer one specific
One of both of which may be selected in interface, if never called, default thinks that selection is located away from the mode of common Binder.
As a kind of optimal technical scheme, when the mode for being located away from common Binder mechanism in operation or it is embedded in common
Further include following procedure before the mode of Binder mechanism:
It reads configuration or the interface called by user obtains which kind of mode user selects, be located away from common Binder mechanism if selecting
Mode, then be located away from the mode operation of common Binder mechanism；If selecting the mode for being embedded in common Binder mechanism, in
Embedded in the mode operation of common Binder mechanism.
As a kind of optimal technical scheme, under the mode for being located away from common Binder, different real-time Binder requests
Between competition, there are two types of processing mode, the first, all real-time Binder requests are impartial to, second, real-time Binder
Request is according to priority ranking；Two ways user can be selected by specific configuration or special interface；It is excellent in the second way
When first grade is default to be set as strong or soft real-time thread priority reaches real-time Binder after certain Binder requests to initiate
Driving sorts by priority the corresponding positions for being inserted into fifo queue under the premise of not interrupting the Binder handled request
It sets.
As a kind of optimal technical scheme, in the mode for being located away from common Binder, there are one in system
ServiceManager or two ServiceManager；
When there are two ServiceManager, one of them is primary ServiceManager, another is special service
In the ServiceManager of real-time Binder, the reservoir area Binder separate be which IPCThreadState class example, so that it may
Corresponding ServiceManager is accessed, to correctly be serviced；
When only existing a ServiceManager, real-time Binder is driven in the service for needing ServiceManager,
The example that the particular interface set by one finds the IPCThreadState class of common Binder, so that access is common
Binder drives to be serviced.
As a kind of optimal technical scheme, there is mark to be to indicate it in the data structure of the fifo queue of real-time Binder
It is no to be requested from real-time Binder.
Compared with the prior art, the present invention has the following beneficial effects:
It is (real-time to single by any one in the mode for being located away from common Binder and the mode for being embedded in common Binder
For Binder request), it requests a possibility that competing real-time Binder request and delay to be preferably minimized common Binder, guarantees
Real-time event or request carry out by Binder mechanism the performance of striding course transmitting.Under both of which, real-time Binder is asked
Asking can all be handled when strong or in soft real-time thread, improve efficiency.Wherein it is located away from the mode of common Binder
A possibility that competition, is preferably minimized.
Detailed description of the invention
Fig. 1 is flow diagram of the invention.
Specific embodiment
Embodiment
The method that real-time Binder processing in real-time Android operation system avoids non real-time Binder competition includes separation
In common Binder mode and/or be embedded in the mode of common Binder, one of mode can be only configured by software
Work, may also be configured to both of which and exists simultaneously, and one of both of which may be selected in software transfer one specific interface,
If never called, default selection is located away from the mode of common Binder.
The above-mentioned mode for being located away from common Binder refers in system in addition to the Binder of Android primary drives and corresponding
Outside device file, there are also the Binder driving of the real-time Binder request of another special service and corresponding device files.It is corresponding
The library device file-Binder in Binder service class and interface class and Binder core classes keeps substantially and primary
Unanimously, the purpose for the arrangement is that in order to allow real-time Binder upper layer application to keep compatible as far as possible with the design of Android primary.
Under the mode for being located away from common Binder, there are two the realities of IPCThreadState class in the same consumer process
Example, the example of respectively common IPCThreadState class and the example of Real-Time IP CThreadState class.One example is the same as general
Logical Binder driving communication, another example drive with real-time Binder and communicate.The Binder service class and interface class on upper layer, with
And it is common Binder request, or Binder request in real time that Binder core classes, which can be distinguished, to find corresponding
The example of IPCThreadState class.Two examples can be located in two difference libraries Binder, may be alternatively located at same
In the library Binder, the example for distinguishing the IPCThreadState class that should be accessed is gone by increased special interface.
Thread in the thread pool of the Example maintenance of common IPCThreadState class is common Android Binder thread,
And the thread in the thread pool of the Example maintenance of Real-Time IP CThreadState class is hard real-time thread or soft real-time thread, in this way
The efficiency for handling real-time Binder request can be improved.It is serviced since real-time Binder request is all driven by real-time Binder, it is real
When Binder driving do not service common Binder request, so Binder request in real time will not request institute competing by common Binder
Strive, competition exists only between different real-time Binder requests, so which solves the competition due to common Binder and
The problem of postponing real-time Binder request.Competition between different real-time Binder requests, there are two types of processing mode, first
Kind, all real-time Binder requests are impartial to, and second, real-time Binder request is according to priority ranking.Two ways is used
Family can be selected by specific configuration or special interface.For the second way it should be noted that priority is default to be set as hard
Real-time or soft real-time thread priority, but user can also modify the priority of Binder request by special interface, when certain
After Binder request is initiated, real-time Binder driving is reached, under the premise of not interrupting the Binder handled request, by excellent
First grade sequence is inserted into the corresponding position of fifo queue (to-do list), and insertion is a set of Binder request, may be more
In the fifo queue (to-do list) of a process.The time of insertion is substantially carried out by primary Binder agreement.
Under the mode for being located away from common Binder, since there are two Binder to drive, and ServiceManager is also
A kind of special Binder service, it is also desirable to drive and communicate with Binder.So there is two kinds of designs here, the first has one
A special service is in the ServiceManager of real-time Binder, as long as it is that the library Binder is distinguished by which IPCThreadState
The example of class.Corresponding ServiceManager can be accessed, to correctly be serviced, this design, in system
There are two ServiceManager.Second is that a ServiceManager is only existed in system, and real-time Binder is being needed
When wanting the service of ServiceManager, the IPCThreadState class of common Binder is found by a special interface
Example, to access common Binder driving to be serviced.Since the service of ServiceManager is only in Binder interface
It is called when initialization, so this design also there is no influence on real-time performance.
The mode for being embedded in common Binder, only deposits a Binder driving in system, and each consumer process is also only
There is the example of an IPCThreadState class.Have in the library Binder additional specific to the real-time Binder interface requested or interface
Parameter, be real-time Binder request or common Binder request to distinguish.When Binder drives to IPCThreadState
When class example request SPAWN thread, by specifically ordering in special parameter or Binder agreement, the line that needs create is indicated
When journey is strong or soft real-time thread, IPCThreadState class example will create corresponding thread to handle in such thread
Real-time Binder request.It is real-time in the corresponding binder_proc structure of each consumer process in Binder driving
Binder request specially maintains the fifo queue of the waiting list rt_wait_queue and real-time Binder of real-time Binder
rt_todo_list.In addition, having mark also in the data structure of the fifo queue of Binder in real time to indicate whether it comes from reality
When Binder request.By this design, reduces real-time Binder request by non real-time Binder and request a possibility that competing.
Although the mode for being embedded in common Binder is not located away from the thorough of the mode of common Binder, it also has advantage, i.e.,
Only one Binder drives in system, the example of only one IPCThreadState class in a process.
In the present embodiment, in system while configured with the mode for being located away from common Binder and being embedded in common Binder
Mode for be specifically described, for each time Binder request be carried out following steps:
Step S1: reading configuration or the interface called by user obtain which kind of mode user selects, and are located away from commonly if selecting
The mode of Binder thens follow the steps S2-1, if the mode for being embedded in common Binder is selected to then follow the steps S3-1;
Step S2-1: the Binder service class and interface class and Binder core classes on upper layer can distinguish Binder request
Property, if real-time IPCThreadState class example is then found in Binder request in real time, if common Binder request is then
Find common IPCThreadState class example；
Step S2-2: real-time Binder request is sent the requests in real time by real-time IPCThreadState class example
Binder driving；It is when the real-time real-time IPCThreadState class example SPAWN of Binder driving request goes out strong or soft real-time
Thread is for handling real-time Binder request；
Step S2-3: real-time Binder driving be impartial to all real-time Binder requests or according to priority them in an orderly manner
It is inserted into the fifo queue of corresponding one or more processes；
S3-1: by the library Binder particular interface or interface parameters indicate that Binder request is a real-time Binder request；
When S3-2:Binder drives to IPCThreadState class example request SPAWN thread, by special parameter or
It is specifically ordered in Binder agreement, when the thread for indicating that needs create is strong or soft real-time thread, IPCThreadState
Class example will create corresponding thread to handle real-time Binder request in such thread；
S3-3: it in the corresponding binder_proc structure of each consumer process, is specially maintained in real time for real-time Binder request
The fifo queue rt_todo_list of the waiting list rt_wait_queue and real-time Binder of Binder.
According to above-described embodiment, the present invention can be realized well.It is worth noting that before based on said structure design
It puts, to solve same technical problem, even if that makes in the present invention is some without substantive change or polishing, is used
Technical solution essence still as the present invention, therefore it should also be as within the scope of the present invention.
Claims (7)
1. the method that the real-time Binder processing in real-time Android operation system avoids non real-time Binder competition, feature exist
In, the following steps are included:
S1: determining the property of Binder request, belongs to real-time Binder request or common Binder request, if in real time
Binder request thens follow the steps S2；
S2:Binder drives to IPCThreadState class example request thread, when SPAWN goes out strong or soft real-time thread with
For handling real-time Binder request;
S3:Binder driving, which is impartial to, all real-time Binde or requests real-time Binder in orderly insertion queue.
2. the real-time Binder processing in real-time Android operation system according to claim 1 avoids non real-time Binder competing
The method striven, which is characterized in that including being located away from the mode of common Binder mechanism and/or being embedded in the mould of common Binder
Formula；
The mode for being located away from common Binder mechanism refers to that there are two Binder driving and corresponding device files in system, respectively
For primary Binder driving and real-time Binder driving；One consumer process there are the example of two IPCThreadState classes,
The example of the example of common IPCThreadState class and real-time IPCThreadState class respectively, for its operation include with
Lower step:
S1a: the Binder service class and interface class and Binder core classes on upper layer can distinguish Binder request property,
If real-time IPCThreadState class example is then found in Binder request in real time, if common Binder request then find it is general
Logical IPCThreadState class example；
S2a: real-time Binder request sends the requests to real-time Binder by real-time IPCThreadState class example and drives
It is dynamic；When the real-time real-time IPCThreadState class example SPAWN of Binder driving request goes out strong or soft real-time thread with
It is requested in handling real-time Binder；
S3a: real-time Binder drives all real-time Binder that are impartial to request or according to priority they are inserted into an orderly manner
Into the fifo queue of corresponding one or more processes；
Be embedded in the mode of common Binder, only deposit Binder driving in system, each consumer process also only one
The example of IPCThreadState class has in the library Binder specific to the real-time Binder interface requested or the additional ginseng of interface
Number is real-time Binder request or common Binder request to distinguish, and operation includes following procedure:
S1b: by the library Binder particular interface or interface parameters indicate that Binder request is a real-time Binder request；
When S2b:Binder drives to IPCThreadState class example request SPAWN thread, by special parameter or
It is specifically ordered in Binder agreement, when the thread for indicating that needs create is strong or soft real-time thread, IPCThreadState
Class example will create corresponding thread to handle real-time Binder request in such thread；
Sb3: it in the corresponding binder_proc structure of each consumer process, is specially maintained in real time for real-time Binder request
The fifo queue rt_todo_list of the waiting list rt_wait_queue and real-time Binder of Binder.
3. the real-time Binder processing in real-time Android operation system according to claim 2 avoids non real-time Binder competing
The method striven, which is characterized in that when system configures above two mode simultaneously, software transfer one specific interface be may be selected
One of both of which, if never called, default thinks that selection is located away from the mode of common Binder.
4. the real-time Binder processing in real-time Android operation system according to claim 3 avoids non real-time Binder competing
The method striven, which is characterized in that when the mode for being located away from common Binder mechanism in operation or be embedded in common Binder mechanism
Mode before further include following procedure:
It reads configuration or the interface called by user obtains which kind of mode user selects, be located away from common Binder mechanism if selecting
Mode, then be located away from the mode operation of common Binder mechanism；If selecting the mode for being embedded in common Binder mechanism, in
Embedded in the mode operation of common Binder mechanism.
5. the real-time Binder processing in real-time Android operation system according to claim 2 avoids non real-time Binder competing
The method striven, which is characterized in that competing between different real-time Binder requests under the mode for being located away from common Binder
It strives, there are two types of processing mode, the first, all real-time Binder requests are impartial to, and second, real-time Binder requests basis
Priority ranking；Two ways user can be selected by specific configuration or special interface；In the second way, priority is default
When ground is set as strong or soft real-time thread priority reaches real-time Binder driving, not after certain Binder requests to initiate
Under the premise of interrupting the Binder request handled, the corresponding position for being inserted into fifo queue is sorted by priority.
6. the real-time Binder processing in real-time Android operation system according to claim 2 avoids non real-time Binder competing
The method striven, which is characterized in that in the mode for being located away from common Binder, there are a ServiceManager or two in system
A ServiceManager；
When there are two ServiceManager, one of them is primary ServiceManager, another is special service
In the ServiceManager of real-time Binder, the reservoir area Binder separate be which IPCThreadState class example, so that it may
Corresponding ServiceManager is accessed, to correctly be serviced；
When only existing a ServiceManager, real-time Binder is driven in the service for needing ServiceManager,
The example that the particular interface set by one finds the IPCThreadState class of common Binder, so that access is common
Binder drives to be serviced.
7. the real-time Binder processing in real-time Android operation system according to claim 2 avoids non real-time Binder competing
The method striven, which is characterized in that have mark in the data structure of the fifo queue of real-time Binder to indicate whether it comes from reality
When Binder request.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910356823.0A CN110196777B (en) | 2019-04-29 | 2019-04-29 | Method for avoiding non-real-time Binder competition in real-time android operating system through real-time Binder processing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910356823.0A CN110196777B (en) | 2019-04-29 | 2019-04-29 | Method for avoiding non-real-time Binder competition in real-time android operating system through real-time Binder processing |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110196777A true CN110196777A (en) | 2019-09-03 |
| CN110196777B CN110196777B (en) | 2023-01-24 |
Family
ID=67752235
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910356823.0A Active CN110196777B (en) | 2019-04-29 | 2019-04-29 | Method for avoiding non-real-time Binder competition in real-time android operating system through real-time Binder processing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110196777B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20150075499A (en) * | 2013-12-26 | 2015-07-06 | 한국전자통신연구원 | Apparatus and method for optimizing system performance of multi-core system |
| CN109117278A (en) * | 2018-06-29 | 2019-01-01 | Oppo（重庆）智能科技有限公司 | A kind of mobile terminal and its method for limiting, the storage medium of interprocess communication |
-
2019
- 2019-04-29 CN CN201910356823.0A patent/CN110196777B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20150075499A (en) * | 2013-12-26 | 2015-07-06 | 한국전자통신연구원 | Apparatus and method for optimizing system performance of multi-core system |
| CN109117278A (en) * | 2018-06-29 | 2019-01-01 | Oppo（重庆）智能科技有限公司 | A kind of mobile terminal and its method for limiting, the storage medium of interprocess communication |
Non-Patent Citations (1)
| Title |
|---|
| STONEDEMO: ""Android HIDL 官方文档（六）—— 使用 Binder 进程间通信机制（Using Binder IPC）"", 《 HTTPS://BLOG.CSDN.NET/QQ_16775897/ARTICLE/DETAILS/78407667 》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110196777B (en) | 2023-01-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106790599B (en) | A kind of symbiosis virtual machine communication method based on multicore without lock buffer circle | |
| CN101354693B (en) | Communication scheduling system and method among cores of isomerization multi-core processor | |
| US6986141B1 (en) | Context controller having instruction-based time slice task switching capability and processor employing the same | |
| CN1008484B (en) | Processor i/o and interrupt filters | |
| CN1760839A (en) | Apparatus, system, and method for facilitating port testing of a multi-port host adapter | |
| CN102331977A (en) | Memory controller, processor system and memory access control method | |
| CN102724035B (en) | Encryption and decryption method for encrypt card | |
| CN100530111C (en) | Multi-thread access indirect register scheduling method | |
| CN105183698A (en) | Control processing system and method based on multi-kernel DSP | |
| CN107077390A (en) | A kind of task processing method and network interface card | |
| CN105550029B (en) | A kind of process scheduling method and device | |
| CN104461970B (en) | Dma controller, mobile terminal and data method for carrying | |
| CN1282085C (en) | Method of parallel regulating multi-task of imbedding system | |
| CN109992366A (en) | Method for scheduling task and dispatching device | |
| CN101290590A (en) | Embedded operating system task switching method and unit | |
| CN101794239B (en) | Multiprocessor task scheduling management method based on data flow model | |
| CN104978174A (en) | Method and system for switching network cards in plurality of operating systems | |
| CN103677959B (en) | A kind of virtual machine cluster migration method and system based on multicast | |
| CN110196777A (en) | The method that real-time Binder processing in real-time Android operation system avoids non real-time Binder competition | |
| CN109992432A (en) | A kind of data processing system and method based on message queue | |
| CN111653317A (en) | Gene comparison accelerating device, method and system | |
| CN102929800A (en) | Cache consistency protocol derivation processing method | |
| CN105893036A (en) | Compatible accelerator extension method for embedded system | |
| EP2113841A1 (en) | Allocating resources in a multicore environment | |
| CN106462360A (en) | Resource scheduling method and related apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |