Just managed to answer my own question - it's purely for the 'break'. Seems
like just putting an 'else { }' would be easier.

-- Nathan

> -----Original Message-----
> From: Neulinger, Nathan [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 19, 2001 4:14 PM
> To: '[EMAIL PROTECTED]'
> Subject: [OpenAFS-devel] question about code in afs_dcache.c
> 
> 
> 
>     if (afs_discardDCList == NULLIDX && afs_freeDCList == NULLIDX) {
>         while (1) {
>         if (!setLocks) avc->states |= CDCLock;
>         afs_GetDownD(5, (int*)0);   /* just need slots */
>         if (!setLocks) avc->states &= (~CDCLock);
>         if (afs_discardDCList != NULLIDX || afs_freeDCList != NULLIDX)
>             break;
>         /* If we can't get space for 5 mins we give up and panic */
>         if (++downDCount > 300)
>             osi_Panic("getdcache");
>         MReleaseWriteLock(&afs_xdcache);
>         afs_osi_Wait(1000, 0, 0);
>         goto RetryLookup;
>         }
> 
> 
> why the while loop? I can't see any way the code would ever 
> get to repeat
> the loop? (Solaris cc complains about end-of-loop code not 
> being reachable
> as well.)
> 
> -- Nathan
> 
> ------------------------------------------------------------
> Nathan Neulinger                       EMail:  [EMAIL PROTECTED]
> University of Missouri - Rolla         Phone: (573) 341-4841
> Computing Services                       Fax: (573) 341-4216
> _______________________________________________
> OpenAFS-devel mailing list
> [EMAIL PROTECTED]
> https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel
> 
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo.cgi/openafs-devel

Reply via email to