Jens Axboe wrote:
Yeah, I'm afraid so. We really should be returning EAGAIN or something like that for the congested condition, though.
How would user mode know when it was safe to retry the request? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: async I/O seems to be blocking on 2.6.15
- From: Jens Axboe <[email protected]>
- Re: async I/O seems to be blocking on 2.6.15
- References:
- async I/O seems to be blocking on 2.6.15
- From: Brent Baccala <[email protected]>
- Re: async I/O seems to be blocking on 2.6.15
- From: Jens Axboe <[email protected]>
- Re: async I/O seems to be blocking on 2.6.15
- From: Brent Baccala <[email protected]>
- Re: async I/O seems to be blocking on 2.6.15
- From: Jens Axboe <[email protected]>
- Re: async I/O seems to be blocking on 2.6.15
- From: Brent Baccala <[email protected]>
- Re: async I/O seems to be blocking on 2.6.15
- From: Jens Axboe <[email protected]>
- async I/O seems to be blocking on 2.6.15
- Prev by Date: Re: [RFC: 2.6 patch] bcm43xx_sprom_write(): add error checks
- Next by Date: Re: SCSI over USB showstopper bug?
- Previous by thread: Re: async I/O seems to be blocking on 2.6.15
- Next by thread: Re: async I/O seems to be blocking on 2.6.15
- Index(es):
 |