[OpenAFS] Windows client tuning question

[Mike Polek]

First, I'd like to start out by saying that since getting some
serious (paid for) support from Jeff Altman last year for our
Windows client woes (well ... more like photoshop woes, but they
weren't interested in fixing the issue), our end-user complaints
for Windows systems has gone to near zero. Best $$ I ever spent
on software support. ;-)  Thanks Jeff.

I currently have an end user claiming that if he does a lot
of very heavy I/O for a couple days, his client will lock up.
I have not yet observed this myself. I just became aware of
it. He's been restarting the client on his own.

Checking the RX stats for the machines in question, I note that
the "noPackets" count is non-zero... and I'm curious if there
is some RX tuning that needs to be done to give the client
more network resources to deal with the heavy traffic.
I recently posted about an issue I was having with the linux
client, and increasing the number of preallocated RX packets
solved my bottleneck issue there.

I looked in the "Advanced" tab for client configuration,
but didn't see anything that looked like it could be adjusted
in a way that would help me out. Any ideas/tips/pointers?

Thanks in advance for any/all advice. RX output is below.

Mike Polek

----------------------------------------------------

Free packets: 572, packet reclaims: 0, calls: 251885, used FDs: 0
not waiting for packets.
0 calls waiting for a thread
1 threads are idle
rx stats: free packets 572, allocs 197127971, alloc-failures(rcv 0/0,send 
0/0,ack 0)
    greedy 0, bogusReads 0 (last from host 0), noPackets 132, noBuffers 0, 
selects 0, sendSelects 0
    packets read: data 103149324 ack 46790492 busy 0 abort 4441 ackall 0 
challenge 671 response 0 debug 6 params 0 unused 0 unused 0 unused 0 version 0
    other read counters: data 103149179, ack 46785734, dup 19122 spurious 
4160 dally 737
    packets sent: data 93664145 ack 74443743 busy 0 abort 3 ackall 0 
challenge 0 response 671 debug 0 params 0 unused 0 unused 0 unused 0 version 0
    other send counters: ack 74443743, data 187328290 (not resends), resends 
3503, pushed 0, acked&ignored 18305082
         (these should be small) sendFailed 0, fatalErrors 1
    Average rtt is 0.001, with 45344867 samples
    Minimum rtt is 0.000, maximum is 54.344
    32 server connections, 189 client connections, 36 peer structs, 102 call 
structs, 101 free call structs


and

Free packets: 53, packet reclaims: 0, calls: 4163, used FDs: 0
not waiting for packets.
0 calls waiting for a thread
1 threads are idle
rx stats: free packets 53, allocs 1180276, alloc-failures(rcv 0/0,send 
0/0,ack 0)
    greedy 0, bogusReads 0 (last from host 0), noPackets 63, noBuffers 0, 
selects 0, sendSelects 0
    packets read: data 819668 ack 168396 busy 0 abort 216 ackall 0 challenge 
42 response 0 debug 5 params 0 unused 0 unused 0 unused 0 version 0
    other read counters: data 819668, ack 168384, dup 0 spurious 4 dally 6
    packets sent: data 350009 ack 519934 busy 0 abort 0 ackall 0 challenge 0 
response 42 debug 0 params 0 unused 0 unused 0 unused 0 version 0
    other send counters: ack 519934, data 700018 (not resends), resends 33, 
pushed 0, acked&ignored 51235
         (these should be small) sendFailed 0, fatalErrors 0
    Average rtt is 0.001, with 157734 samples
    Minimum rtt is 0.000, maximum is 0.125
    22 server connections, 1 client connections, 22 peer structs, 52 call 
structs, 52 free call structs