flock(fd, LOCK_UN) taking 500ms+ ?

• Next message: Krishnakumar B: "Keyboard problems with Linux-2.5.40"
• Previous message: Johannes Erdfelt: "Re: Multiple OOPS with Linux-2.5.40"
• Next in thread: John Levon: "Re: flock(fd, LOCK_UN) taking 500ms+ ?"
• Reply: John Levon: "Re: flock(fd, LOCK_UN) taking 500ms+ ?"
• Maybe reply: Manfred Spraul: "Re: flock(fd, LOCK_UN) taking 500ms+ ?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

In 2.5.40, our application is getting seemingly very large
flock(LOCK_UN) latencies :

Unlock, took 541386 usecs
Old was 567999237 secs, 131042 usecs
now is 567999237 secs, 672428 usecs
Unlock, took 125083 usecs
Old was 567999237 secs, 699310 usecs
now is 567999237 secs, 824393 usecs
Unlock, took 151245 usecs
Old was 567999237 secs, 825119 usecs
now is 567999237 secs, 976364 usecs

(using gettimeofday ...)

No similar times are observed during the corresponding LOCK_EX call.

Is this just a silly app bug somewhere, or something funny in locks.c ?

More details, testing etc. on request ...

regards
john

-- 
"I never understood what's so hard about picking a unique
 first and last name - and not going beyond the 6 character limit."
 	- Toon Moene
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

• Next message: Krishnakumar B: "Keyboard problems with Linux-2.5.40"
• Previous message: Johannes Erdfelt: "Re: Multiple OOPS with Linux-2.5.40"
• Next in thread: John Levon: "Re: flock(fd, LOCK_UN) taking 500ms+ ?"
• Reply: John Levon: "Re: flock(fd, LOCK_UN) taking 500ms+ ?"
• Maybe reply: Manfred Spraul: "Re: flock(fd, LOCK_UN) taking 500ms+ ?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:31 EST