Shuichi Oikawa’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 (30)


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.


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.


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.


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.





A Feasibility Study of Hybrid Dram and Flash Memory Management Unit

September 2014

·

28 Reads

·

1 Citation

In this research, we propose the flash memory aware memory management unit (MMU) that enables an efficient hybrid memory architecture. We design the proposed MMU based on the SSDAlloc hybrid memory architecture to make flash memory aware. Our challenge is to make flash memory suitable for hybrid memory architecture, which consists of DRAM and flash memory and works as main memory. The proposed MMU can reduce the overhead of the runtime library implementation, and improve the DRAM utilization efficiency. As a result, the proposed MMU can reduces more than half of page fault.


Citations (14)


... 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

... Before ARM Virtualization Extensions became available, paravirtualization approach are often proposed. Suzuki et al. [28] analyzed ARM architecture and constructed par- avirtualization hypervisor on ARM architecture. Their eval- uation showed their hypervisor suffered from various over- heads. ...

Analysis of the ARM Architecture’s Ability to Support a Virtual Machine Monitor through a Simple Implementation
  • Citing Article
  • January 2013

International Journal of Networking and Computing

... 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

... Kgil et al. [5] proposed FlashCache using flash as a disk cache which can enhance disk performance but not main memory. Some proposals realized hybrid memory with hardware extension [6], [7]. The software approaches using SSD as a main memory extension will be introduced in detail in the next section. ...

A Feasibility Study of Hybrid Dram and Flash Memory Management Unit
  • Citing Article
  • September 2014

... 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

... Studies Alternative NVM application [4], [9], [21], [34], [41], [46], [58], [60], [59], [63], [66], [71], [74], [91], [112], [144] Alternative software layer design [15], [19], [24], [40], [42], [44], [48], [60], [61], [69], [73], [74], [85], [82], [92], [119], [129] Surveys [5], [14], [21], [35], [39], [77], [93], [94], [101], [102], [106], [111], [117], [122], [133], [137], [140] File system design [3], [9], [17], [25], [29], [33], [32], [37], [41], [45], [57], [58], [67], [76], [75], [99], [100], [98], [105], [104], [120], [123], [126], [130], [131], [136], [138], [144] Novel architecture design [3], [12], [14], [13], [11], [20], [23], [30], [33], [34], [32], [47], [49], [51], [57], [65], [76], [90], [99], [98], [97], [105], [104], [110], [112], [123], [124], [131], [132], [141], [143], [144] Standalone technique or method [4], [8], [13], [17], [20], [22], [19], [30], [31], [36], [43], [47], [49], [50], [51], [53], [54], [56], [58], [60], [63], [62], [69], [68], [66], [70], [71], [81], [79], [80], [78], [87], [83], [88], [86], [85], [89], [92], [91], [97], [103], [109], [112], [114], [115], [116], [118], [125], [127], [132], [134], [135], [142] propose file system hybrid approaches. In these approaches, the idea is to combine the best of both technologies, by, for example, using NVM to store frequently accessed data or using it for logging/journaling while using NAND Flash as back storage. ...

File-Based Memory Management for Non-volatile Main Memory
  • Citing Conference Paper
  • July 2013

... (3) persistent object management. We tailor the design of SIMPO to hybrid main memory architecture which is also adopted by many research studies (Wu and Zwaenepoel 1994;Saito and Oikawa 2012;Bailey et al. 2011). While NVRAM candidates like STT-RAM have the potential to completely replace DRAM, a volatile area of main memory is still desirable for program execution (particularly considering 2-4× higher write latency in current STT-RAM technologies for instance). ...

Exploration of Non-volatile Memory Management in the OS Kernel
  • Citing Conference Paper
  • December 2012

... There are at least the following two limitations; 1) the classification of the sensitive instructions into the privileged and non-privileged ones is not verified since there is no guarantee that the emulator behaves exactly the same as real hardware especially for the sensitive instructions, and 2) the execution of the emulator makes it impossible to analyze the performance impact. We also worked on the analysis of the sensitive instructions and the development of our VMM on the emulator, and reported the results [25,26] earlier than KVM/ARM. We then moved our work on real hardware. ...

SIVARM: A Virtual Machine Monitor for the ARM architecture
  • Citing Article
  • November 2010