Messages in this thread | | | Date | Tue, 13 Apr 1999 22:15:38 +0200 (CEST) | From | Peter-Paul Witta <> | Subject | linux nfs update latency |
| |
-----BEGIN PGP SIGNED MESSAGE-----
hi!
consider the following:
p1 flocks file /nfs/a , opens it for update, reads record # 100, modifies it and writes it to disk.
p2 does the same as p1, but is started after the read of p1.
i did read in "distributed systems" that it *** can *** take up to 3 seconds for the client to receive update information (nfs cache latency).
i guess the upper system will work anyway (consider the update as "add 10 to value") without losing counts?
kind regards, http://surf.to/paul.witta Peter-Paul Witta e9525748@student.tuwien.ac.at 436765411293@max.mail.at SAMBA SUPPORT - FAX SOLUTIONS - INTRANET / EXTRANET - DBMS SQL SOLUTIONS
-----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv
iQCVAwUBNxOl7f3CItW+OrlZAQGWSQP/eIHaRbVA1+wqz8WfJDA6NcOt3ee2ZvK+ 009hBd/p7gaZtbtO2G3Wepd9mFD4mD/wOSBbDv06RH4jghx1hVWV3C/ytOVvRIXL TZPdvGPxGbT7ceub9AyqipQey0F8YzYSaoxAgt2Sdt5e1XbNm2UigySm5ENkQX23 c5T66bXceR8= =uxpJ -----END PGP SIGNATURE-----
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |