{'fraction_non_alphanumeric': 0.028417818740399385, 'fraction_numerical': 0.0030721966205837174, 'mean_word_length': 5.204761904761905, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
An Alternative Fast Packet I/O with Native System Calls

This paper proposes an alternative high-speed packet I/O that enables user-space applications to receive and transmit packets at high speeds using the read() and write() system call families. Recent high-speed packet I/O frameworks have opened up new application designs optimized for network performance. However, they have two obstacles to implementing applications: restraints on programming models and limitations on NICs. These frameworks provide applications with APIs to access packets in kernel space without memory copies instead of well-generalized APIs, such as the socket API. Thus, the applications would be tightly coupled with the framework-specific APIs, and would be forced to adopt the APIs' programming models. Moreover, typical frameworks require specific NICs, which the frameworks support for their optimization. In contrast, the proposed packet I/O, called hpio, adapts native system calls for the packet I/O API and works with native device drivers. These advantages offer developers an easy way to implement various high-speed applications. Our measurement results demonstrate that hpio achieved over 40 Mpps with 60-byte packets, although it involves memory copies on system calls and no optimization of packet buffers.