At Sun, 09 Oct 2005 16:37:59 -0400, Jonathan S. Shapiro wrote: > Conceptually, the solution that we use in Coyotos is simple: we place > the burden of supplying storage on the client rather than on the server. > In any operation that allocates storage, the client supplies a "Space > Bank" object from which the server allocates the storage on behalf of > this client. > > To simplify the protocols, it is normal for the client to specify a > space bank at object creation time. The server associates this bank with > the object for later use when that object is extended, grown, or shrunk.
How does the client determine how large a space bank to hand to the server? In the case of an object upon which the client depends, I can see the argument that no limit need be provided. On the other hand, a task might have a number of resources that it would like to use but doesn't depend on. If it gives unlimited access to its space bank then one misbehaving server can create a denial of service. What does the server do when it requires more storage but the space bank is full? Does it send a reply to the client indicating that it needs a larger space bank and it is up to the client to provide up resources or abort the operation? Thanks, Neal _______________________________________________ L4-hurd mailing list [email protected] http://lists.gnu.org/mailman/listinfo/l4-hurd
