EXECUTION METHOD AND APPARATUS

• US 20150293701A1
• Filed: 04/09/2015
• Published: 10/15/2015
• Est. Priority Date: 04/09/2014
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: KIM, Kwonsik, LEE, Hyojeong, LIM, Seyoun, KIM, Myungsun, HAN, Sangbok, PARK, Jongchul
• Granted Patent: US 10,275,158 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 12/121 using replacement algorithms
• CPC Class Codes: G06F 13/14 Handling requests for interconnection or transfer
• CPC Class Codes: G06F 2212/70 Details relating to dynamic memory management
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/0652 Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
• CPC Class Codes: G06F 3/0653 Monitoring storage devices or systems
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/0671 In-line storage system
• CPC Class Codes: G06F 3/0673 Single storage device
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

An application execution method for improving the operation speed of the application in executing or in the middle of running the application is provided. The application execution method includes detecting a launch of an application, preloading Input/Outputs (I/Os) requested at the launch based on profile data with I/Os requested at a previous launch of the application, and updating the profile data based on at least one of the I/Os requested at current and previous launches of the application.

Claims

1. An application execution method of a terminal, the application execution method comprising:

detecting a launch of an application;

preloading Input/Outputs (I/Os) requested at the launch based on profile data with I/Os requested at a previous launch of the application; and

updating the profile data based on at least one of the I/Os requested at current and previous launches of the application.

2. The method of claim 1, wherein the updating of the profile data comprises:

determining whether the I/Os requested at the launch of the application exist in the profile data; and

adding, when the I/Os do not exist in the profile data, the I/Os to the profile data.

3. The method of claim 1, wherein the updating of the profile data comprises determining whether the I/Os requested at the launch of the application are related to launching the application.

4. The method of claim 3, wherein the determining of whether the I/Os requested at the launch of the application are related to launching the application comprises determining whether Inter-Processor Communication occurs between the I/Os requested at the launch of the application and the I/Os stored in the profile data.

5. The method of claim 1, wherein the updating of the profile data comprises:

determining I/Os to be included in the profile data; and

merging the I/Os which can be merged among the I/Os to be included in the profile data.

6. The method of claim 5, wherein the merging of the I/Os comprises:

extracting the I/Os associated with a same file among the I/Os to be included in the profile data;

determining whether the I/Os associated with the same file are within a time range preconfigured for merging; and

merging, when the I/Os associated with the same file are within the time range, the I/Os associated with the same file.

7. The method of claim 1, further comprising checking, after the detecting of the launch of the application, a memory state of the terminal.

8. The method of claim 7, wherein the checking of the memory state comprises determining, when a free memory amount of the terminal is less than a first threshold, that the memory state is a low memory level at which the terminal preloads only the Input/Outputs (I/Os) requested by the application among the I/Os included in the profile data.

9. The method of claim 7, wherein the checking of the memory state comprises determining, when the free memory amount of the terminal is greater than a second threshold, that the memory state is a high memory level at which the terminal preloads all of the I/Os included in the profile data.

10. The method of claim 7, wherein the checking of the memory state comprises determining, when the free memory amount of the terminal is in a range between a first threshold and a second threshold, that the memory state is a normal memory level at which the terminal preloads the I/Os in proportion to a ratio of the free memory amount to whole memory size among the I/Os included in the profile data.

11. A terminal for executing an application, the terminal comprising:

a storage unit configured to store profile data including a list of Input/Outputs (I/Os) requested at a previous launch of the application; and

a control unit configured to;

detect a launch of an application;

preload I/Os requested at the launch based on profile data with I/Os requested at the previous launch of the application; and

update the profile data based on at least one of the I/Os requested at current and previous launches of the application.

12. The terminal of claim 11, wherein the control unit is further configured to:

determine whether the I/Os requested at the launch of the application exist in the profile data; and

add, when the I/Os do not exist in the profile data, the I/Os to the profile data.

13. The terminal of claim 11, wherein the control unit is further configured to determine whether the I/Os requested at the launch of the application are related to launching the application.

14. The terminal of claim 13, wherein the control unit is further configured to determine whether Inter-Processor Communication occurs between the I/Os requested at the launch of the application and the I/Os stored in the profile data.

15. The terminal of claim 11, wherein the control unit is further configured to:

determine I/Os to be included in the profile data; and

merge the I/Os which can be merged among the I/Os to be included in the profile data.

16. The terminal of claim 15, wherein the control unit is further configured to:

extract the I/Os associated with a same file among the I/Os to be included in the profile data;

determine whether the I/Os associated with the same file are within a time range preconfigured for merging; and

merge, when the I/Os associated with the same file are within the time range, the I/Os associated with the same file.

17. The terminal of claim 11, wherein the control unit checks, after detecting the launch of the application, a memory state of the terminal.

18. The terminal of claim 17, wherein the control unit is further configured to determine, when free memory amount of the terminal is less than a first threshold, that the memory state is a low memory level at which the terminal preloads only the I/Os requested by the application among the I/Os included in the profile data.

19. The terminal of claim 17, wherein the control unit is further configured to determine, when the free memory amount of the terminal is greater than a second threshold, that the memory state is a high memory level at which the terminal preloads all of the I/Os included in the profile data.

20. The terminal of claim 17, wherein the control unit is further configured to determine, when the free memory amount of the terminal is in a range between a first threshold and a second threshold, that the memory state is a normal memory level at which the terminal preloads the I/Os in proportion to a ratio of the free memory amount to whole memory size among the I/Os included in the profile data.

21. An application execution method of a terminal, the application execution method comprising:

detecting a memory return request of a process executed by the application;

storing memory mapping information of the process in response to the memory return request;

determining whether a total amount of the memory mapping information stored in the memory mapping storage is greater than a predetermined capacity; and

releasing, when the total amount of the memory mapping information is greater than the predetermined capacity, a connection between a virtual memory and a physical memory which is associated with at least one memory mapping information in units of page.

22. The method of claim 21, wherein the releasing of the connection comprises:

deleting the at least one memory mapping information from the memory mapping storage; and

releasing the connection between the virtual and physical memories by page.

23. The method of claim 21, further comprising transferring, when the application generates a request for at least one memory mapping information stored in the memory mapping storage, the memory mapping information as much as requested to the application.

24. The method of claim 21, wherein the predetermined capacity is equal to or greater than a size of the physical memory.

25. A terminal for executing an application, the terminal comprising:

a physical memory unit configured to store data;

an input unit configured to receive an input to generate a request signal of the application;

a virtual memory unit configured to map the data stored in the physical memory unit;

a memory mapping storage configured to;

detect a memory return request of a process executed by the application; and

store the memory mapping information of the process in response to the memory return request; and

a control unit configured to;

determine whether total amount of the memory mapping information stored in the memory mapping storage is greater than a predetermined capacity; and

release, when the total amount of the memory mapping information is greater than the predetermined capacity, a connection between the virtual memory unit and the physical memory which is associated with at least one memory mapping information in units of page.

26. The terminal of claim 25, wherein the control unit is further configured to:

delete the at least one memory mapping information from the memory mapping storage; and

release the connection between the virtual and physical memories by page.

27. The terminal of claim 25, wherein the control unit is further configured to transfer, when the application generates a request for at least one memory mapping information stored in the memory mapping storage, the memory mapping information as much as requested to the application.

28. The terminal of claim 25, wherein the predetermined capacity is equal to or greater than a size of the physical memory.