[AFS3-std] Re: [OpenAFS-devel] convergence of RxOSD, Extended Call Backs, Byte Range Locking, etc.

[Matt W. Benjamin]

Hi Hartmut,

Does using GetODSDlocation and StoreMini as begin/end I/O RPCs allow use of an opaque identifier to refer to an I/O transaction?

Matt

----- "Hartmut Reuter" <reuter@rzg.mpg.de> wrote:

> Tom's idea to have a Start-of-I/O-rpc and a Stop-I/O-rpc to enforce
> data
> consistency is great. I think it would not be very difficult to
> implement this.
> 
> Caching of the information returned by GetOSDlocation could reduce
> traffic on the wire, but is not really essential. So if we still do
> one
> GetOSDlocation per I/O we can use GetOSDlocaltion as
> Start-of-I/O-rpc.
> 
> So for write I would propose that the fileserver has to keep the
> information about Fid, offset, length, host, and time in a table or
> chain and keep it there until the storeMini has happened. So also
> extended callbacks for file ranges would become possible. For the
> write
> case storeMini would function as End-of-I/O-rpc.

-- 

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309