On Tue, Dec 2, 2008 at 11:04 AM, Steve Dickson <SteveD@xxxxxxxxxx> wrote: > Kevin Coffman wrote: >> Hi Neil, >> This seems reasonable. >> >> I have a patch somewhere that gets the actual Kerberos expiration that >> could be used for the rsc timeout. But I think this should be fine >> for now. (Perhaps at the cost of requiring clients to negotiate a new >> context every hour?) > This question is a bit worrisome, imho... I understand the need to release > memory consumed by dead contexts but on the other hand, renegotiating > contexts every hour on the hours seems a bit costly as well... > > Does it make sense to make this time out configurable? Yes, it would be > a very obscure knob, but in the unlikely event there is a bug in the > renegotiating code or renegotiating simply becomes too costly, I think > it would good to have a way to dial the time out back up as a work-around. > > steved. Hi Steve, Rather than adding another config knob, how 'bout I dust off my patch to get the "right" timeout value? I should be able to make that available tomorrow. (I have limited resources to work on this at the moment.) K.C. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
