Redesigning Xen's Memory Sharing Mechanism for Safe and Efficient I/O Virtualization

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Redesigning Xen's Memory Sharing Mechanism for Safe and Efficient I/O Virtualization
# 1  
Old 03-22-2010
Redesigning Xen's Memory Sharing Mechanism for Safe and Efficient I/O Virtualization

HPL-2010-39 Redesigning Xen's Memory Sharing Mechanism for Safe and Efficient I/O Virtualization - Ram, Kaushik Kumar; Santos, Jose Renato; Turner, Yoshio
Keyword(s): No keywords available.
Abstract: Xen's memory sharing mechanism, called the grant mechanism, is used to share I/O buffers in guest domains' memory with a driver domain. Previous studies have identified the grant mechanism as a significant source of network I/O overhead in Xen. This paper describes a redesigned grant mechanism to si ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Efficient UNIX Memory management for Running MapReduce Jobs.

We are trying to set up a single node cloudera hadoop cluster having 16 GB as RAM on linux machine. We are setting up 5.4.2 version. Now when we check statistics post the installation and run the top command we find that only 1 -2 GB is available. when we trigger map reduce sample job - no... (2 Replies)
Discussion started by: ketankirange
2 Replies

2. Programming

SQL redesigning

The following request give the expected result (respecting a certain output formatting) But i was wondering if the same result could be produced in a more "optimized way" (Oracle 9i by the way) set feedback off set pagesize 0 set trimspool on ttitle off btitle off set verify off set... (3 Replies)
Discussion started by: ctsgnb
3 Replies

3. Programming

Memory sharing with NCURSES

Hey, Im using a shared memory segment to share a WINDOW structure among 2 processes. Basically I'm building a multi-player snake game in which multiple prrocesses access the window. The 'parent' process initializes the shared memory segment and puts the window in it. I can access and perform... (1 Reply)
Discussion started by: dgre0018
1 Replies

4. Solaris

Async-Signal-Safe versus MT-Safe

Hi, I am Solaris 9 developer and notice that the documentation does not provide a clear notion of the inherent concurrency in routines defined as "Async-Signal-Safe". Routines defined as "MT-Safe" obviously have the best level of concurrency, compared to normal "Safe" interfaces. I have... (1 Reply)
Discussion started by: tristan12
1 Replies

5. Programming

memory sharing - not shared memory -

hi, this is the problem: i want to swap a linked list between 4 processes (unrelated), is there any way i can do that just by sending a pointer to a structure? //example typedef struct node { int x; char c; struct node *next; } node; or i should send the items ( x,c ) by... (9 Replies)
Discussion started by: elzalem
9 Replies

6. IP Networking

sharing of IP address for load sharing avoiding virtual server & redirection machine

I have RedHat 9.0 installed on three of my servers (PIII - 233MHz) and want that they share a common IP address so that any request made reaches each of the servers. Can anyone suggest how should I setup my LAN. I'm new to networking in Linux so please elaborate and would be thankful for a timely... (2 Replies)
Discussion started by: Rakesh Ranjan
2 Replies

7. UNIX for Advanced & Expert Users

mmap vs shared memory - which is best for sharing data between applications?

Between mmap and shared memory which is the best method of sharing data between multiple applications, interms of speed? (2 Replies)
Discussion started by: nmds
2 Replies
Login or Register to Ask a Question
XENTRACE_FORMAT(1)					      General Commands Manual						XENTRACE_FORMAT(1)

NAME
xentrace_format - pretty-print Xen trace data SYNOPSIS
xentrace_format [ DEFS-FILE ] DESCRIPTION
xentrace_format parses trace data in xentrace binary format from standard input and reformats it according to the rules in a file of defi- nitions (DEFS-FILE), printing to standard output. The rules in DEFS-FILE should have the format shown below: event_id whitespace format Each rule should start on a new line. The format string may include format specifiers, such as: %(cpu)d, %(tsc)d, %(event)d, %(1)d, %(2)d, %(3)d, %(4)d, %(5)d [ the `d' format specifier output in decimal, alternatively `x' will output in hexadecimal and `o' will output in octal ] These correspond to the CPU number, event ID, timestamp counter and the 5 data fields from the trace record. There should be one such rule for each type of event to be pretty-printed (events which do not have formatting rules are ignored). A sample format file for Xen's predefined trace events is available in the file tools/xentrace/formats in the Xen source tree. Depending on your system and the rate at which trace data is produced, this script may not be able to keep up with the output of xentrace if it is piped directly. In these circumstances you should have xentrace output to a file for processing off-line. AUTHOR
Mark A. Williamson <mark.a.williamson@intel.com> SEE ALSO
xentrace(8), xentrace_cpusplit(1) Xen domain 0 utils 11 May 2004 XENTRACE_FORMAT(1)