I have check my code, the unlink is done after the close.
> -----Original Message-----
> From: Trond Myklebust [mailto:[email protected]]
> Sent: Monday, August 12, 2002 8:55 PM
> To: Brasseur Val=E9ry
> Cc: [email protected]
> Subject: Re: [NFS] nfs unlink perf !
>=20
>=20
> >>>>> " " =3D=3D Brasseur Val=E9ry <[email protected]> =
writes:
>=20
> > I am testing an application which to a lot of link/unlink
> > server is a NetApp filer, client is linux 2.4.19+nfs patches.
>=20
> > under load it seems that the unlink call is very long when all
> > over calls response time seems to be OK. is there any =
problems
> > with the unlink code ?
>=20
> There should be no problems, but it depends on what type of test you
> are doing...
>=20
> The NFS protocol has to work around some nasty compatibility problems
> w.r.t. the POSIX expected behaviour of unlink. In particular, POSIX
> allows you to do
>=20
> open(file);
> write(file);
> unlink(file);
> read(file);
> close(file);
>=20
> i.e. to unlink an open file...
>=20
> In order for the above to work with NFS, one can't immediately unlink
> the file when it is open(). Instead, NFS does a 'sillyrename': it
> renames the file to something of the form .nfsXXXXX (where XXXX is
> some number) and then performs the unlink when the 'close()' has been
> performed.
>=20
> Would this suffice to explain your 'bad performance'?
>=20
> Cheers,
> Trond
>=20
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs