> > What about adding something to the NBD protocol which tells the server > > that x requests are coming in and that the client will not wait for an > > acknowledgement before it has send all requests and/or data for those x > > requests? > > Because then a server can pull in all requests in one go and then start > > to fiddle with the disk. Or do things intelligent in parallel (if you > > have multiple spindels). etc. > > I don't see why we need to change the protocol for that? It's already > possible to handle requests in parallel. The client can (and does) > alrady have multiple outstanding requests; it's just that the current > server implementation doesn't handle them in parallel.
Problem is that a server does not know that it can wait for more requests to come in for which it can wait. With the enhancement it knows that it can input multiple requests and then process them. Like iSCSI does. Folkert van Heusden -- ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
