[OpenAFS] afs memcache tuning... lockups in afs_cv_wait

[Derrick Brashear]

1) get better backtraces (see the personal reply)
2) either you have more threads than that, or you have more serious problems...


>    From what I can tell, RX wants to allocate a packet
> to send data on the network, but there are none available,
> so it decides to just hang out and wait, assuming that
> a response will come back from the file server eventually,
> somebody will free up a packet, and things will continue.
> In the previous posts, I believe it was stated that packets
> did come back from the file server, but perhaps were not
> processed by the client. I'm wondering if there is some
> sort of race condition where when things get busy, the
> client can't process the returning packets, and everything
> just deadlocks.