[Samba] Slower performance on oplock

[Li, Ying (ESG)]

Hi Volker,

Thanks for your response.

> No idea. A signal sometimes not delivered?
No. If that signal was received, there was no delay. If it's not received, the delay occurred. Look at the message from a client log file.

[2008/01/31 11:58:41, 3] smbd/open.c:delay_for_oplocks(683)
  Sending break request to PID 24330
[2008/01/31 11:58:41, 3] smbd/open.c:defer_open(741)
  defer_open_sharing_error: time [1201809521.237026] adding deferred open entry for mid 6
5344
[2008/01/31 11:58:41, 3] smbd/process.c:push_deferred_smb_message(220)
  push_deferred_open_smb_message: pushing message len 148 mid 65344 timeout time [1201809
581.237026]
[2008/01/31 11:58:41, 3] smbd/process.c:push_queued_message(113)
  push_message: pushed message length 148 on deferred_open_queue
[2008/01/31 11:58:41, 3] smbd/process.c:open_was_deferred(179)
  open_was_deferred
[*** a delay for the time OPLOCK_TIMEOUT*2   ***]
[2008/01/31 11:59:41, 3] smbd/process.c:switch_message(1010)
  switch message SMBntcreateX (pid 25366) conn 0x8b2a10


> Does the message end up in messages.tdb?
How to check out if it's end up. I use tdbdump on messages.tdb. Looks like ending up. Just a huge data with 8192bytes presented on the entry for that pid. I'm wondering whether there was possibility of msgbuf overflow because its length is 1600 in message.c.
key(10) = "PID/24330\00"
data(2992) = "<huge data>"

I'm looking for what reason to cause the signal missing.

Thanks.
-Ying