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
sasl_errors(10 July 2001)												 sasl_errors(10 July 2001)

NAME
sasl_errors - SASL error codes SYNOPSIS
#include <sasl/sasl.h> DESCRIPTION
The following are the general error codes that may be returned by calls into the SASL library, and their meanings (that may vary slightly based on context): Common Result Codes SASL_OK Success SASL_CONTINUE Another step is needed in authentication SASL_FAIL Generic Failure SASL_NOMEM Memory shortage failure SASL_BUFOVER Overflowed buffer SASL_NOMECH Mechanism not supported / No mechanisms matched requirements SASL_BADPROT Bad / Invalid Protocol or Protocol cancel SASL_NOTDONE Can't request information / Not applicable until later in exchange SASL_BADPARAM Invalid Parameter Supplied SASL_TRYAGAIN Transient Failure (e.g. weak key) SASL_BADMAC Integrity Check Failed SASL_NOTINIT SASL library not initialized Client-only Result Codes SASL_INTERACT Needs user interaction SASL_BADSERV Server failed mutual authentication step SASL_WRONGMECH Mechanism does not support requested feature Server-only Result Codes SASL_BADAUTH Authentication Failure SASL_NOAUTHZ Authorization Failure SASL_TOOWEAK Mechanism too weak for this user SASL_ENCRYPT Encryption needed to use mechanism SASL_TRANS One time use of a plaintext password will enable requested mechanism for user SASL_EXPIRED Passphrase expired, must be reset SASL_DISABLED Account Disabled SASL_NOUSER User Not Found SASL_BADVERS Version mismatch with plug-in SASL_NOVERIFY USer exists, but no verifier for user Password Setting Result Codes SASL_PWLOCK Passphrase locked SASL_NOCHANGE Requested change was not needed SASL_WEAKPASS Passphrase is too week for security policy. SASL_NOUSERPASS User supplied passwords are not permitted CONFORMING TO
RFC 2222 SEE ALSO
sasl(3) SASL man pages SASL sasl_errors(10 July 2001)