Gaku Nakagawa’s research while affiliated with University of Tsukuba and other places

What is this page?


This page lists works of an author who doesn't have a ResearchGate profile or hasn't added the works to their profile yet. It is automatically generated from public (personal) data to further our legitimate goal of comprehensive and accurate scientific recordkeeping. If you are this author and want this page removed, please let us know.

Publications (13)


Behavior-Based Memory Resource Management for Container-Based Virtualization
  • Conference Paper

December 2016

·

10 Reads

·

8 Citations

Gaku Nakagawa

·

Shuichi Oikawa

Fork Bomb Attack Mitigation by Process Resource Quarantine

November 2016

·

80 Reads

·

6 Citations

A fork bomb attack is a denial of service attack. An attacker generates many processes rapidly, exhausting the resources of the target computer systems. There are several previous work to detect and remove the processes that cause fork bomb attacks. However, the operating system with the previous methods have the risks to terminate inappropriate processes that do not fork bomb processes. In this paper, we propose a new method that named process resource quarantine. With the proposed method, the operating systems don't terminate the detected fork bomb processes. Instead of the termination, the operating systems make resource limitations for the detected processes and inspect them periodically. We implemented the proposed method on Linux kernel and executed several evaluation experiments. The results show that the proposed method is effective for fork bomb attacks mitigation.


Using DRAM as Cache for Non-Volatile Main Memory Swapping

January 2016

·

19 Reads

The performance of mobile devices such as smartphones and tablets has been rapidly improving in recent years. However, these improvements have been seriously affecting power consumption. One of the greatest challenges is to achieve efficient power management for battery-equipped mobile devices. To solve this problem, the authors focus on the emerging non-volatile memory NVM, which has been receiving increasing attention in recent years. Since its performance is comparable with that of DRAM, it is possible to replace the main memory with NVM, thereby reducing power consumption. However, the price and capacity of NVM are problematic. Therefore, the authors provide a large memory space without performance degradation by combining NVM with other memory devices. In this study, they propose a design for non-volatile main memory systems that use DRAM as a swap space. This enables both high performance and energy efficient memory management through dynamic power management in NVM and DRAM.


Modeling Energy Consumption of Memory Systems

December 2015

·

23 Reads

·

1 Citation

Hirotaka Kawata

·

Gaku Nakagawa

·

·

[...]

·

Shuichi Oikawa

The energy consumption of memory is one of the important metrics to evaluate memory systems. However, previous approaches such as using cycle accurate CPU and memory simulators require a long execution time for simulation. We are developing a model of energy consumption of DRAM-and NVM-based main memory, which allows estimating the energy consumption of a memory subsystem from easily observable performance metrics in real computer systems. In this paper, we conducted preliminary experiments using various types of workloads and observed the correlation of the memory throughput and energy consumption of DRAM. We used hardware performance counters to obtain memory throughput and energy consumption with minimum performance overhead.


Out of Memory Prevention Based on Memory Allocation Rate

December 2015

·

6 Reads

·

2 Citations

The amount of free memory have a great influence on system stability because out of memory occurs performance degradation phenomena, unexpected process terminations and so on. Thus, It is an important administration task to design the memory utilization plan based on the characteristics of the processes. However, in sometimes, processes demand a large amount of main memory rapidly and unexpectedly due to various reasons (e.g. memory leaks, malicious programs, denial of service attacks to network servers). These unexpected large memory demands cause out of memory and make the systems unstable. Existing memory management mechanisms are somewhat effective to prevent such out of memory with the unexpected memory demands. However, the existing mechanisms have several problems arising from the difficulty in the discrimination between the expected and unexpected large memory demands. As a solution, we propose a new memory resource management method at the operating system level. The proposed method utilizes memory allocation rate to detect unexpected large memory demands, i.e., the operating system with the proposed methods regard the processes that demand memory rapidly as offending processes. In this paper, we will discuss the problem of existing memory management mechanism and describe the proposed method and show the evaluation experiments.


Multi-level queue NVM/DRAM hybrid memory management with language runtime support

October 2015

·

27 Reads

·

1 Citation

Non-volatile memory devices (NVM) devices, such as PCM, STT-MRAM, and ReRAM, enable the integration of secondary storage into main memory. This integration reduces I/O access to slow block devices; however, it is currently unrealistic to construct a large capacity main memory with a single NVM, because such devices have certain write access limitations. Combining NVM and other memory devices is necessary to overcome such disadvantages. Several researches discussed NVM/DRAM hybrid memory, combining NVM and DRAM. To use NVM/DRAM hybrid memory, the placement of data between NVM and DRAM must be determined. In particular, write-hot data should be allocated to DRAM and write-cold data to NVM. For data placement, programming language runtime supports are useful because they possess more detailed information about write access than the operating systems. A previous research proposed the individual counting method to manage NVM/DRAM hybrid memory with programming language runtime support that determine data placement based on the number of write accesses to each object. However, it is difficult to determine dynamically threshold values for data placements using the individual counting method. Here we propose a multi-level queue method to distinguish between write-hot and write-cold data. Experimental results show that the proposed method resolves the limitations of the individual counting method.




An Analysis of the Relationship between a Write Access Reduction Method for NVM/DRAM Hybrid Memory with Programming Language Runtime Support and Execution Policies of Garbage Collection

September 2014

·

5 Reads

·

2 Citations

There are several research projects about new generation non-volatile memory (NVM), such as STT-MRAM, PCM and ReRAM. Non-volatile main memory makes it possible to integrate secondary storages in main memory. The integration enables to reduce I/O to slow block devices. It is, however, impossible to construct large capacity main memory with a single NVM in this point. It is required to combine DRAM and NVM or combine NVM and another NVM to construct unified non-volatile main memory. The previous researches discussed NVM/DRAM hybrid main memory architecture, which combine PCM and DRAM. In our previous work, we proposed a method to manage NVM/DRAM hybrid main memory with programming language runtimes supports. Language runtimes, such as Java runtimes, have more detailed informaion about write acceess to data than operating system has. The language runtime supports are useful to manage NVM/DRAM hybrid memory therefore. In the proposed method, the runtime migrates objects between NVM and DRAM based on the characteristics of write access. The language runtime executes the migration processes during garbage collection processes. The performance of the proposed method rely on the frequency of garbage collection. In this paper, we will discuss and do an experiment about how the frequency of garbage collection effects the performance of the proposed method. The results of the experiment shows that the improved method cut 91 percent of write access. The results also show that the improved method cut 50 percent of the usage of DRAM.


Language runtime support for NVM/DRAM hybrid main memory

April 2014

·

11 Reads

·

6 Citations

Replacing of DRAM in main memory with non-volatile memory (NVM) has several merits. However, NVM under development has some limitations in write operation. To overcome it, some previous researches proposed NVM/DRAM hybrid memory architecture. In the architecture, it needs to determine data placements between NVM and DRAM. In this paper, we advocate that programming language runtimes are useful for management of NVM/DRAM hybrid main memory. In addition, we will propose a method to manage NVM/DRAM hybrid main memory with language runtime support.


Citations (4)


... One such core cloud computing technology gaining more traction over the years is container-based virtualization (Portworx, 2019). Container-based virtualization is an operating system-level virtualization approach with less overhead than hypervisor virtualization (Nakagawa & Oikawa, 2016) so it can help industries by having flexibility and scalability features which create significant cost savings (Dewi et al., 2019). ...

Reference:

Analysis of Load Balancing Least Connection and Shortest Expected Delay Algorithm for Web Server Using Kube-Proxy on Kubernetes
Behavior-Based Memory Resource Management for Container-Based Virtualization
  • Citing Conference Paper
  • December 2016

... Depleting all available CPU and memory resources leads the FSW to hang or crash, forcing the satellite into a predefined recovery process. The malicious script in this scenario contains the infamous fork bomb, more formally known as the "rabbit virus" [22]. The fork bomb uses the fork system call, commonly found within a Unix-based or Linux OS. ...

Fork Bomb Attack Mitigation by Process Resource Quarantine
  • Citing Conference Paper
  • November 2016

... In the remainder of this section, we tried to examine some selected solutions, which include different hybrid main memory architecture models given in works listed on Table 1. [12], [13], [14], [15], [16], [17], [18], [19], [20], [21], [22], [23], [24], [25], [26] 2 DRAM + PRAM [27], [28], [29], [30], [31], [32], [33], [34], [35], [36] 3 DRAM + NVM [37], [38], [39], [40], [41] 4 ...

Language runtime support for NVM/DRAM hybrid main memory
  • Citing Conference Paper
  • April 2014