| To: | Kelledin <kelledin+XFS@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: bug? sv_wait() and gcc3 |
| From: | Steve Lord <lord@xxxxxxx> |
| Date: | 12 May 2003 20:16:00 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <200305121748.41157.kelledin+XFS@xxxxxxxxxxxxxxxxxxx> |
| References: | <200305101230.28794.kelledin+XFS@xxxxxxxxxxxxxxxxxxx> <200305121748.41157.kelledin+XFS@xxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Mon, 2003-05-12 at 17:48, Kelledin wrote: > Further details: > > I investigated sv_wait, and it seems that function/macro is > intended to deliberately schedule a non-interruptible deadlock > for as long as the platform will allow (MAX_SCHEDULE_TIMEOUT). > That's a pretty long time in jiffies--and on platforms where > long ints are 64 bits (like Alpha), it's an outrageously long > time. This is intended to be a wait without a timeout, not a very long timeout. sv_wait is being used to block one thread pending a signal from another thread. Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: bug? sv_wait() and gcc3, Kelledin |
|---|---|
| Next by Date: | Re: bug? sv_wait() and gcc3, Kelledin |
| Previous by Thread: | Re: bug? sv_wait() and gcc3, Kelledin |
| Next by Thread: | Re: bug? sv_wait() and gcc3, Kelledin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |