Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 10,000 papers for “Address space”

Internet Address Space

Marcelo Bagnulo · OECD digital economy papers · 2008

The report provides an analysis of economic considerations associated with the transition from IPv4 to IPv6. It provides background analysis supporting the forthcoming ICCP-organised Ministerial-level meeting on -The Future of the Internet Economy, to take place in Seoul, Korea on 17-18 June 2008.

Cited by 0Open access

Address space management.

Min Wu (41570), Wenfeng Ying (19226353) · Figshare · 2024

<div><p>Aiming at the problems of data integration and information sharing in the calibration workshop of smoke alarm, combining OPC Unified Architecture (OPC UA) and digital twin technology, the OPC UA based digital twin smoke alarm calibration workshop information network framework is proposed. Using OPC UA information modeling technology, a digital workshop information model for smoke alarm calibration was constructed, and the static attribute set, process attribute set, and functional component set of the workshop were defined in detail. Taking the smoke box as an example, the information model construction was instantiated, and data collection and transmission were carried out with the digital twin model of the smoke box, achieving the implementation mapping between the twin model and physical entities. The results show that based on the proposed OPC UA information model, the interconnection and intercommunication of data at all levels of the digital twin smoke alarm calibration workshop can be achieved, and the workshop can be visualized, digitized, and flexible.</p></div>

Cited by 0Open access

Single Address Space Or Private Address Spaces ?

Jacques Mossi, Xavier Rousset De Pina · 1994

this paper is organized as follows. In section 2 are discussed two different schemes for protection, both relying upon the capability concept. Section 3 gives an argument for the use of private data, and shows that they can be implemented at low cost. Section 4 outlines a proposal in which a shared single address space for persistent data coexists with private segments for temporary data. In conclusion, this proposal is compared to previous systems.

Cited by 0

Address to Outer Space

Nancy Smith · Journal of Health Physical Education Recreation · 1961

(1961). Address to Outer Space. Journal of Health, Physical Education, Recreation: Vol. 32, No. 6, pp. 65-66.

Cited by 0

Network Address Translation: Extending the Internet Address Space

Dan Wing · IEEE Internet Computing · 2010

Network Address Translation (NAT) and Network Address and Port Translation (NAPT) are widely used to separate networks and share IPv4 addresses. They're valuable tools for network administrators and help with the imminent exhaustion of IPv4 address space and the transition to IPv6. This article surveys recent standardization efforts in this area.

Cited by 51

Coordinated Address Space Management architecture

Weiping Xu, Jun Bi, Rakesh Kumar et al. · 2018

IP addresses work as a basic element for providing broadband network services. However, the increase in number, diversity and complexity of modern network devices and services creates unprecedented challenges for the currently prevailing approach of manual IP address management. Manually maintaining IP addresses could always be sub- optimal for IP resource utilization. Besides, it requires heavy human effort from network operators. To achieve high utilization and flexible scheduling of IP network addresses, it is necessary to automate the address scheduling process. This document describes an architecture for the IP address space management. It includes architectural concepts and components used in the CASM (Coordinated Address Space Management), with a focus on those interfaces to be standardized in the IETF.

Cited by 0

Programming Shared Address Space Platforms

2001

Explicit parallel programming requires specification of parallel tasks along with their interactions. These interactions may be in the form of synchronization or communication of intermediate results. In shared address space architectures, communication is implicitly specified since some (or all) of the memory is accessible to all the processors. Consequently, programming paradigms for shared address space machines support constructs for expressing concurrency and synchronization along with techniques for minimizing associated overheads. In this chapter, we will discuss shared-address-space programming paradigms along with their performance aspects and related extensions to directive-based languages. As we briefly discussed in Chapter??, shared address space programming paradigms can vary widely on issues of data sharing, concurrency models, and support for synchronization. Process based models assume that all data associated with a process is private by default unless otherwise specified. While this is important for ensuring protection in multiuser systems, it is not necessary when multiple concurrent aggregates are cooperating to solve the same problem. The overheads associated with enforcing protection domains make processes less suitable for parallel programming. In contrast, lightweight processes and threads assume that all memory is global. By relaxing the protection domain, lightweight processes and threads support much faster manipulation. As a result, this is the preferred programming model for parallel programming and will be discussed extensively in this chapter. Directive based programming models extend the threaded model by facilitating creation and synchronization of threads. In this chapter, we study various aspects of programming using threads and parallel directives.

Cited by 0

procmaps: Portable Address Space Mapping

Kirill Müller · 2020

Portable '/proc/self/maps' as a data frame. Determine which library or other region is mapped to a specific address of a process. – R packages can contain native code, compiled to shared libraries at build or installation time. When loaded, each shared library occupies a portion of the address space of the main process. When only a machine instruction pointer is available (e.g. from a backtrace during error inspection or profiling), the address space map determines which library this instruction pointer corresponds to.

Cited by 0Open access

IPv4 with Adaptive Address Space

Ramamurthy R. Ati, Abraham Chen · 2016

This document describes a solution to the Internet address depletion issue through the use of an existing Option mechanism that is part of the original IPv4 protocol. This proposal, named EzIP (phonetic for Easy IPv4), discusses the IPv4 public address pool expansion and the Internet system architecture enhancement aspects. It was originated by a study called ExIP (Extended IPv4) analyzing the use of the first available octet (eight bits) in the reserved private network pools (10/8, 172.16/12 and 192.168/16) to achieve a moderate address space expansion factor of 256 by each, while maintaining their familiar operation characteristics. Along the way, a parallel yet similar effort, called EnIP (Enhanced IPv4), was discovered. EnIP fully utilizes the same private network pools to increase the address space by a factor of 17.1M with end-to-end connectivity. EzIP is a superset that proposes one unified format for not only encompassing the considerations of both, but also identifying additional capabilities and flexibilities. For example, EzIP may expand an IPv4 address at least by a factor of 256 to as high as 256M without affecting the existing IPv4 public address assignments, while still keeping intact the current private networks for the 256M case if desired. The EzIP is in full conformance with the IPv4 protocol, and supports not only both categories of connectivity, but also their interoperability. The traditional Internet traffic and the IoT operations may coexist simultaneously without perturbing their existing setups, while offering end-users the freedom to choose one or the other. If the IPv4 public pool were reorganized, the assignable pool could be multiplied by 512M or even up to 2B times with end-to-end connectivity. EzIP may be deployed as a firmware enhancement to the Internet edge routers or private network gateways wherever needed, or simply installed as an inline adjunct module between the two, enabling a seamless introduction. The 256M case establishes a spherical layer of routers providing a complete interconnection between the Internet and end- users. This configuration enables the entire current Internet and private networks characteristics to remain intact. These proposed interim facilities would afford IPv6 more time to orderly reach the maturity and the availability levels required for delivering a long- term general service.

Cited by 0

A Distributed Single Address-Space . . .

Gernot Heiser, Kevin Elphinstone, Stephen Russell et al. · 1993

Persistence has long been difficult to integrate into operating systems. The main problem is that pointers lose their meaning once they are taken out of their address-space. We present a distributed system which has a single address-space encompassing all virtual memory of every node in the system. This design has become possible (and practicable) with the advent of 64-bit microprocessors. In our system

Cited by 0