CN112445778B - File operation method and file operation system based on VxWorks - Google Patents
File operation method and file operation system based on VxWorks Download PDFInfo
- Publication number
- CN112445778B CN112445778B CN201910838641.7A CN201910838641A CN112445778B CN 112445778 B CN112445778 B CN 112445778B CN 201910838641 A CN201910838641 A CN 201910838641A CN 112445778 B CN112445778 B CN 112445778B
- Authority
- CN
- China
- Prior art keywords
- file
- memory
- file system
- target
- state information
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000004590 computer program Methods 0.000 claims description 9
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 2
- 230000007717 exclusion Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000000638 solvent extraction Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- FYYHWMGAXLPEAU-UHFFFAOYSA-N Magnesium Chemical compound [Mg] FYYHWMGAXLPEAU-UHFFFAOYSA-N 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 229910052749 magnesium Inorganic materials 0.000 description 1
- 239000011777 magnesium Substances 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/188—Virtual file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a file operation method and a file operation system based on VxWorks, wherein the method comprises the following steps: the target file system receives a file operation instruction sent by a user and transmits the file operation instruction to a target driving system corresponding to the target file system; the target file system is one of a plurality of file systems, and each file system is mounted on the same memory through different driving systems; based on the transferred file operation instruction, the target drive system acquires state information of the memory, wherein the state information comprises information used for representing whether the memory is currently occupied by other file systems except the target file system; and when the state of the memory is determined to be idle, the target driving system obtains the operation authority of the memory so as to enable the memory to execute corresponding operation instructions.
Description
Technical Field
The present invention relates to VxWorks operating systems, and in particular, to a method, a system, a computer device, and a computer readable storage medium for operating a VxWorks-based file system.
Background
The existing VxWorks file system architecture is to run a hardware management layer TFFS on the FLASH hardware, and use the TFFS to manage and operate the whole hardware of the FLASH, as shown in fig. 1. A DOS file system is operated on the TFFS, and a standard file operation interface is provided for an upper layer. However, due to various drawbacks of the storage architecture, such as non-power-down security, no erasure equalization, etc., the storage architecture is a natural disadvantage in application scenarios where files stored on FLASH are frequently erased. If the traditional architecture is used for frequently erasing file operation, if the single board is abnormally powered off, the file system is likely to crash, and other files stored in the file system (such as a start script) cannot be read, so that the function of the single board is directly disabled. In another case, the erasure lifetime of each sector in the traditional NOR FLASH is only 10 ten thousand times, the native TFFS layer does not implement a specific erasure balancing algorithm, that is, there may be a case that a certain sector has been erased 10 ten thousand times, and there may be another sector that is unused at a time, and in NOR FLASH, as long as there is a sector failure, the file system mounted on the sector may not be mounted, the file system fails, and all files are lost. This is intolerable for some industries where safety requirements are high, such as aerospace, rail transit, medical. Therefore, how to extend the service life and the functions of FLASH under the condition of limited hardware resources is a technical problem to be solved by those skilled in the art.
Disclosure of Invention
The invention aims to provide a file system operation method, a file system operation system, computer equipment and a computer readable storage medium based on VxWorks, so as to solve the problems in the prior art.
In order to achieve the above purpose, the present invention provides a VxWorks-based file operation method, which includes the following steps:
The target file system receives a file operation instruction sent by a user and transmits the file operation instruction to a target driving system corresponding to the target file system; the target file system is one of a plurality of file systems, and each file system is mounted on the same memory through different driving systems;
based on the transferred file operation instruction, the target drive system acquires state information of the memory, wherein the state information comprises information used for representing whether the memory is currently occupied by other file systems except the target file system;
And when the state of the memory is determined to be idle, the target driving system obtains the operation authority of the memory so as to enable the memory to execute corresponding file operation instructions.
According to the file operation method based on VxWorks provided by the invention, the step of acquiring the state information of the memory by the target driving system comprises the following steps:
the target driving system acquires busy state information, idle state information or error state information of the memory;
Wherein the busy state information characterizes that the memory is currently being operated by other file systems, the idle state information characterizes that the memory is not currently being operated by other file systems, and the error state information characterizes that the current operation state of the memory is not known.
According to the file operation method based on VxWorks provided by the invention, the step of executing the corresponding file operation instruction on the memory by the target drive system comprises the following steps:
The target drive system executes corresponding file operation in a target storage space of the memory, wherein the target storage space is a pre-allocated address space corresponding to the target file system, and the pre-allocated address spaces of different file systems are different from each other.
According to the VxWorks-based file operation method provided by the invention, the target file system receives a file operation instruction sent by a user, and before the step of transmitting the file operation instruction to a target drive system corresponding to the target file system, the method further comprises the following steps:
The target file system acquires the operation type of a file operation instruction sent by a user, and determines whether to receive the file operation instruction according to the operation type; the operation types comprise read-only operation and read-write operation.
According to the VxWorks-based file operation method, the file systems comprise read-only file systems and read-write file systems, wherein the read-only file systems are used for receiving read-only file operation instructions sent by users, and the read-write file systems are used for receiving read-write file operation instructions sent by the users.
According to the VxWorks-based file operation method, the file systems comprise DOS file systems and a reference file system, wherein a driving system corresponding to the DOS file systems is a TFFS system, and a driving system corresponding to the reference file system is a FlashFX system.
According to the VxWorks-based file operation method provided by the invention, the DOS file system is a read-only file system, and the reference file system is a read-write file system.
In order to achieve the above object, the present invention further provides a VxWorks-based file operating system, including:
The file system is used for receiving a file operation instruction sent by a user and transmitting the file operation instruction to a driving system corresponding to the file system, wherein the file system comprises a DOS file system and a Reliance file system which are mounted on the same memory;
The driving system is used for receiving the file operation instruction and operating data in a corresponding address space in the memory, and comprises a TFFS driving system corresponding to the DOS file system and a FlashFX driving system corresponding to the Reliance file system;
And the memory is used for storing the file system and the driving system and accepting the operation of the driving system.
To achieve the above object, the present invention also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method when executing the computer program.
To achieve the above object, the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the above method.
The file operation method and the file operation system based on VxWorks provided by the invention provide a flexible solution for reasonably distributing hardware flash resources and configuring different file systems for different operation data. The invention can mount a plurality of file systems and corresponding driving systems on the same FLASH, and each file system corresponds to different file objects so as to achieve the purpose of classifying read-only files and read-write files into different file systems. The invention simultaneously carries out mutual exclusion management on a plurality of file systems, namely only one file system is allowed to operate FLASH at the same time, so that the plurality of file systems can be mounted in the same FLASH without mutual interference. Furthermore, by introducing a FlashFX +repeat architecture, the invention can achieve the beneficial effects of power-down safety and erasing balance.
Drawings
FIG. 1 is a schematic diagram of a conventional VxWorks file system architecture;
FIG. 2 is a schematic diagram of a file operating system according to an embodiment of the present invention;
FIG. 3 is a flowchart of a second embodiment of a file manipulation method according to the present invention;
FIG. 4 is a schematic diagram illustrating a program module of a third embodiment of a file manipulation apparatus according to the present invention;
fig. 5 is a schematic hardware structure of a third embodiment of the file operating device of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The method, the device and the system for operating the file based on the VxWorks, provided by the invention, provide a flexible solution for reasonably distributing hardware flash resources and configuring different file systems for different operation data. The invention can mount a plurality of file systems and corresponding driving systems on the same FLASH, and each file system corresponds to different file objects so as to achieve the purpose of classifying read-only files and read-write files into different file systems. The invention simultaneously carries out mutual exclusion management on a plurality of file systems, namely only one file system is allowed to operate FLASH at the same time, so that the plurality of file systems can be mounted in the same FLASH without mutual interference. Furthermore, by introducing a FlashFX +repeat architecture, the invention can achieve the beneficial effects of power-down safety and erasing balance.
Example 1
Referring to fig. 2, the present embodiment provides a VxWorks-based file operating system, including:
The file system is used for receiving a file operation instruction sent by a user and transmitting the file operation instruction to a driving system corresponding to the file system, wherein the file system comprises a DOS file system and a Reliance file system which are mounted on the same memory;
The driving system is used for receiving the file operation instruction and operating data in a corresponding address space in the memory, and comprises a TFFS driving system corresponding to the DOS file system and a FlashFX driving system corresponding to the Reliance file system;
And the memory is used for storing the file system and the driving system and accepting the operation of the driving system. Wherein, the memory is preferably FLASH memory.
According to the invention, a plurality of file systems are mounted on the same FLASH, and each file system is provided with a corresponding driving system, so that each file system can operate the FLASH through the corresponding driving system. In the invention, a plurality of file systems are mounted on the same FLASH in a partitioning mode. The partitioning means that the FLASH is divided into a plurality of memory spaces according to different addresses in advance, and the addresses of the memory spaces are different from one another. Further, each storage space corresponds to a file system.
According to a specific application scenario of the invention, a DOS file system and a Reliance file system are simultaneously mounted on the same FLASH, wherein a driving system corresponding to the DOS file system is a TFFS driving system, and a driving system corresponding to the Reliance file system is a FlashFX driving system, so that a TFFS+DOS architecture and a FlashFX +reliance architecture are respectively formed on the same FLASH.
The partition of tffs+dos is a native storage architecture, and has features of simple migration, rich interfaces, etc., so that it is used for storing some read-only files needed by vxworks, such as start script, version information, etc. The FlashFX +repeat architecture has the advantages of safe power failure, balanced erasure, configurable index submission mode and the like, and when a file system mounted on FLASH is used for carrying out frequent read-write operation on the file, the problem that the file system is destructively influenced due to abnormal power failure is not needed, and the problem of the service life of the sector of the FLASH is also not needed. With the equalization component, lifetime can be calculated by:
Lifetime (year) = (sector number) ×105/(frequency of use (times/day) ×365)
The FLASH of magnesium light, mt28ew128, is used for calculation, the size of the sector is 128KB, the FLASH capacity is 16MB, and the total number of the sectors is 128, the use frequency is assumed to be 200 times per day, and the service life is approximately 175 years after calculation.
It can be understood by those skilled in the art that the above architecture of simultaneously mounting one DOS file system and one reference file system on the same FLASH is only one example, and the invention can also mount more than two file systems on the same FLASH, for example, simultaneously mount multiple DOS file systems and multiple reference file systems. In addition, specific operations of different file systems can be set according to actual conditions, and the method is not limited to a mode of performing read-only operation on a DOS file system and performing read-write operation on a reference file system, and one or more DOS file systems can be set to perform read-only operation, and other DOS file systems and reference file systems can perform read-write operation and the like. In short, any architecture in which a plurality of file systems are mounted on the same FLASH belongs to the protection scope of the present invention.
Example two
Referring to fig. 3, the present invention provides a VxWorks-based file operation method, which includes the following steps:
S1, a target file system receives a file operation instruction sent by a user and transmits the file operation instruction to a target driving system corresponding to the target file system; the target file system is one of a plurality of file systems, and each file system is mounted on the same memory through a different driving system.
When a user sends a file operation instruction to one of a plurality of file systems, the target file system firstly forwards the received file operation instruction to a corresponding target driving system so that the target driving system can perform corresponding operation on a memory according to the file operation instruction.
The multiple file systems in the invention are simultaneously mounted on the same hardware memory such as FLASH. The plurality of file systems in the present invention may include, in particular, a DOS file system and a Reliance file system.
S2, based on the file operation instruction, the target drive system acquires state information of the memory, wherein the state information comprises information used for representing whether the memory is currently occupied by other file systems except the target file system.
And responding to a file operation instruction sent by the target file system, and acquiring the state information of the memory by the target drive system corresponding to the target file system. By acquiring state information of a memory is meant acquiring information whether the memory is currently operated by other file systems.
In order to achieve simultaneous mounting of multiple file systems on the same FLASH, the invention provides that one file system is allowed to operate on the memory at the same time. Thus, after receiving the file operation instruction, the target drive system needs to first acquire whether the memory is currently available, that is, whether other file systems are operating on the memory. If no other file system is currently operating the memory, the target drive system acquires idle state information; if other file systems are currently operating the memory, the target drive system acquires busy state information; if it is not known whether other file systems are currently operating the memory within the specified time, the target drive system may acquire error status information.
The drive system in the present invention may specifically include a TFFS drive system corresponding to the DOS file system and a FlashFX drive system corresponding to the Reliance file system.
And S3, when the state of the memory is determined to be idle, the target driving system obtains the operation authority of the memory so as to enable the memory to execute a corresponding file operation instruction.
When the target drive system acquires the idle state information, it is indicated that no other file system is currently operating the memory, so that the target drive system can operate the memory in the target storage space according to the received file operation instruction.
The target storage space refers to a storage space which is pre-allocated in the memory and corresponds to the target file system, wherein the address of the storage space corresponding to each file system is different, and each file system can only operate in the pre-allocated corresponding storage space. For example, a first storage space is allocated for a first file system, a second storage space is allocated for a second file system, and a third storage space is allocated for a third file system, wherein address ranges of the first storage space, the second storage space, and the third storage space are different.
Example III
With continued reference to fig. 4, a VxWorks-based file manipulation apparatus is shown, in which the file manipulation apparatus 10 may include or be divided into one or more program modules, which are stored in a storage medium and executed by one or more processors to accomplish the present invention and implement the above-described file manipulation method. Program modules in the present invention refer to a series of computer program instruction segments capable of performing a specific function, which are more suitable than the program itself for describing the execution of the file operation apparatus 10 in a storage medium. The following description will specifically describe functions of each program module of the present embodiment:
The instruction receiving module 11 is suitable for receiving a file operation instruction sent by a user by a target file system and transmitting the file operation instruction to a target driving system corresponding to the target file system; the target file system is one of a plurality of file systems, and each file system is mounted on the same memory through different driving systems;
a state receiving module 12, adapted to obtain, based on the transferred file operation instruction, state information of the memory, where the state information includes information for characterizing whether the memory is currently occupied by a file system other than the target file system;
and the execution module 13 is suitable for obtaining the operation authority of the memory by the target drive system when the state of the memory is determined to be idle, so that the memory executes corresponding file operation instructions.
According to the VxWorks-based file operation apparatus provided by the present invention, the state receiving module 12 includes:
A busy state unit 121, adapted to receive, by the target drive system, busy state information returned by the target drive system, where the busy state information characterizes that the memory is currently being operated by other file systems;
An idle state unit 122, adapted to receive, by the target drive system, idle state information returned by the target drive system, where the idle state information characterizes that the memory is not currently operated by other file systems;
The error state unit 123 is adapted to receive, by the target driving system, error state information returned by the target driving system, where the error state information characterizes that the current operation state of the memory is not known.
According to the VxWorks-based file operation apparatus provided by the present invention, the execution module 13 includes:
The storage space executing unit 131 is adapted to execute corresponding file operations in a target storage space of the memory by the target drive system, where the target storage space is a storage space pre-allocated corresponding to the target file system, and the storage spaces pre-allocated by different file systems have different addresses.
The present embodiment also provides a computer device, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack-mounted server, a blade server, a tower server, or a rack-mounted server (including an independent server or a server cluster formed by a plurality of servers) that can execute a program. The computer device 20 of the present embodiment includes at least, but is not limited to: a memory 21, a processor 22, which may be communicatively coupled to each other via a system bus, as shown in fig. 3. It should be noted that fig. 3 only shows a computer device 20 having components 21-22, but it should be understood that not all of the illustrated components are required to be implemented, and that more or fewer components may be implemented instead.
In the present embodiment, the memory 21 (i.e., readable storage medium) includes a flash memory, a hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the memory 21 may be an internal storage unit of the computer device 20, such as a hard disk or memory of the computer device 20. In other embodiments, the memory 21 may also be an external storage device of the computer device 20, such as a plug-in hard disk provided on the computer device 20, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD), or the like. Of course, the memory 21 may also include both internal storage units of the computer device 20 and external storage devices. In this embodiment, the memory 21 is typically used to store an operating system and various types of application software installed on the computer device 20, such as program codes of the file operation apparatus 10 of the third embodiment. Further, the memory 21 may be used to temporarily store various types of data that have been output or are to be output.
Processor 22 may be a central processing unit (Central Processing Unit, CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 22 is generally used to control the overall operation of the computer device 20. In this embodiment, the processor 22 is configured to execute the program code stored in the memory 21 or process data, for example, execute the file operation apparatus 10, to implement the file operation method of the second embodiment.
The present embodiment also provides a computer-readable storage medium such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application store, etc., on which a computer program is stored, which when executed by a processor, performs the corresponding functions. The computer-readable storage medium of the present embodiment is used to store the file operation apparatus 10, and when executed by a processor, implements the file operation method of the second embodiment.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
It will be appreciated by those of ordinary skill in the art that all or part of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable medium, where the program when executed includes one or a combination of the steps of the method embodiment.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (6)
1. The file operation method based on VxWorks is characterized by comprising the following steps of:
the target file system acquires the operation type of a file operation instruction sent by a user, and determines whether to receive the file operation instruction according to the operation type; the operation type comprises read-only operation and read-write operation;
The target file system receives a file operation instruction sent by a user and transmits the file operation instruction to a target driving system corresponding to the target file system; the target file system is one of a plurality of file systems, and each file system is mounted on the same memory through different driving systems; the file systems comprise DOS file systems and a Reliance file system, wherein a driving system corresponding to the DOS file systems is a TFFS system, and a driving system corresponding to the Reliance file systems is a FlashFX system;
Based on the transferred file operation instruction, the target driving system acquires busy state information, idle state information or error state information of the memory; the busy state information indicates that the memory is currently operated by other file systems, the idle state information indicates that the memory is not currently operated by other file systems, and the error state information indicates that the current operation state of the memory cannot be known;
When the state of the memory is determined to be idle, the target driving system obtains the operation authority of the memory, and executes corresponding file operation in a target storage space of the memory, wherein the target storage space is a pre-allocated address space corresponding to the target file system, and the pre-allocated address spaces of different file systems are different from each other.
2. The VxWorks-based file operation method of claim 1, wherein the plurality of file systems includes a read-only file system and a read-write file system, wherein the read-only file system is configured to receive a read-only file operation instruction issued by a user, and the read-write file system is configured to receive a read-write file operation instruction issued by the user.
3. The VxWorks-based file operation method of claim 1, wherein the DOS file system is a read-only file system and the reference file system is a read-write file system.
4. A VxWorks-based file operating system, comprising:
The file system is used for acquiring the operation type of the file operation instruction sent by the user and determining whether the file operation instruction is received or not according to the operation type; the operation type comprises read-only operation and read-write operation; the file system is also used for receiving a file operation instruction sent by a user and transmitting the file operation instruction to a driving system corresponding to the file system, wherein the file system comprises a DOS file system and a Reliance file system which are mounted on the same memory;
The driving system is used for receiving the file operation instruction and acquiring busy state information, idle state information or error state information of the memory based on the transferred file operation instruction; the busy state information indicates that the memory is currently operated by other file systems, the idle state information indicates that the memory is not currently operated by other file systems, and the error state information indicates that the current operation state of the memory cannot be known; the driving system is further used for obtaining the operation authority of the memory when the state of the memory is determined to be idle, and operating the data in the corresponding address space in the memory, wherein the driving system comprises a TFFS driving system corresponding to a DOS file system and a FlashFX driving system corresponding to a reference file system;
And the memory is used for storing the file system and the driving system and accepting the operation of the driving system.
5. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1 to 3 when the computer program is executed by the processor.
6. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910838641.7A CN112445778B (en) | 2019-09-05 | 2019-09-05 | File operation method and file operation system based on VxWorks |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910838641.7A CN112445778B (en) | 2019-09-05 | 2019-09-05 | File operation method and file operation system based on VxWorks |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112445778A CN112445778A (en) | 2021-03-05 |
| CN112445778B true CN112445778B (en) | 2024-05-28 |
Family
ID=74733248
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910838641.7A Active CN112445778B (en) | 2019-09-05 | 2019-09-05 | File operation method and file operation system based on VxWorks |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112445778B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010009549A (en) * | 2008-06-30 | 2010-01-14 | Toshiba Corp | Data processor and data processing method |
| WO2010060902A1 (en) * | 2008-11-27 | 2010-06-03 | Giesecke & Devrient Gmbh | Memory access to a portable data storage medium |
| CN101901263A (en) * | 2010-07-22 | 2010-12-01 | 华为终端有限公司 | Access method and device of file system |
| WO2012140671A2 (en) * | 2011-04-11 | 2012-10-18 | Ineda Systems Pvt. Ltd | File system sharing |
| CN103810124A (en) * | 2012-11-09 | 2014-05-21 | 辉达公司 | Data transmission system and data transmission method |
-
2019
- 2019-09-05 CN CN201910838641.7A patent/CN112445778B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2010009549A (en) * | 2008-06-30 | 2010-01-14 | Toshiba Corp | Data processor and data processing method |
| WO2010060902A1 (en) * | 2008-11-27 | 2010-06-03 | Giesecke & Devrient Gmbh | Memory access to a portable data storage medium |
| CN101901263A (en) * | 2010-07-22 | 2010-12-01 | 华为终端有限公司 | Access method and device of file system |
| WO2012140671A2 (en) * | 2011-04-11 | 2012-10-18 | Ineda Systems Pvt. Ltd | File system sharing |
| CN103810124A (en) * | 2012-11-09 | 2014-05-21 | 辉达公司 | Data transmission system and data transmission method |
Non-Patent Citations (1)
| Title |
|---|
| 水下自主航行器大容量信息存储的研究与实现;王欢;吴旭光;王慧;;计算机测量与控制(第01期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112445778A (en) | 2021-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110083494B (en) | Method and apparatus for managing hardware errors in a multi-core environment | |
| CN110083399B (en) | Applet running method, computer device and storage medium | |
| CN103365696A (en) | BIOS (Basic Input Output System) image file obtaining method and device | |
| CN103970557A (en) | Storage device and system starting method thereof | |
| CN110716845B (en) | Log information reading method of Android system | |
| EP4036735A1 (en) | Method, apparatus and readable storage medium | |
| CN111104201A (en) | System migration method and device, electronic equipment and storage medium | |
| CN113157290B (en) | Multi-system installation method, computing equipment and storage medium | |
| CN113282351A (en) | Switch starting method and device, electronic equipment and storage medium | |
| CN109213429B (en) | Storage management method and device | |
| US20200363974A1 (en) | System and Method for Tying Non-Volatile Dual Inline Memory Modules to a Particular Information Handling System | |
| CN111124294B (en) | Sector mapping information management method and device, storage medium and equipment | |
| US11221766B2 (en) | System and method for persistent memory rotation based on remaining write endurance | |
| CN112445778B (en) | File operation method and file operation system based on VxWorks | |
| US11340882B2 (en) | Systems and methods for enforcing update policies while applying updates from bootable image file | |
| US20150212866A1 (en) | Management system for service of multiple operating environments, and methods thereof | |
| CN107656702B (en) | Method and system for accelerating hard disk read-write and electronic equipment | |
| CN107422987B (en) | Method and device for storing data in nonvolatile memory | |
| US9971532B2 (en) | GUID partition table based hidden data store system | |
| CN113791874A (en) | Configuration method and device for virtual machine boot, computer equipment and storage medium | |
| CN113849230A (en) | Server starting method and device, electronic equipment and readable storage medium | |
| CN112667444A (en) | System upgrading method, storage medium and terminal equipment | |
| US11144453B2 (en) | Unmap to initialize sectors | |
| CN114443582B (en) | File system mounting method, device, equipment and medium on operating system | |
| CN113535241B (en) | Diskless starting method, diskless starting device, terminal equipment and storage medium |
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 |