[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Potential use case for opaque space bank: domain factored network stack

From: Pierre THIERRY
Subject: Potential use case for opaque space bank: domain factored network stack
Date: Fri, 5 Jan 2007 21:59:51 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

I just read the "Network Subsystems Reloaded" paper by Sinha, Sarat and
Shapiro. Part of it discusses a network stack implemented for EROS with
several isolated processes. As such layout typically lacks performance,
they at least avoid copying accross protection boundaries with shared

A client of the TCP stack would give it access to four memory regions:
two for TCP headers and two for payloads, for transmission and
reception. This avoids DOS attacks by clients because the stack doesn't
use it's own limited memory to work on behalf of it's clients.

But to ensure correctness of network packets, header sections must not
be writable by the client.

With the design of space banks as it was vigourously debated earlier,
would that be even possible? IIRC, it was not considered desirable that
a process A could give authority to some of it's resources (here,
memory) to another process B while losing some of it's own authority to
it (but having the ability to reclaim it back).

Nowhere man
OpenPGP 0xD9D50D8A

Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]