Jeff Mahoney wrote: > No, it's not, and deadlock is definitely possible. However, if we're at > the point where memory is tight enough that it's an issue, the timer can > expire and all the pending i/o is dropped just as it would be without > the multipath code enabled. Followed by requesting a dialog to tell the user that their dirty data/metadata has been dropped :) -- Jamie - 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/
- References:
- [PATCH] Use of getblk differs between locations
- From: Glauber de Oliveira Costa <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Anton Altaparmakov <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Glauber de Oliveira Costa <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Mikulas Patocka <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Anton Altaparmakov <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Mikulas Patocka <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Anton Altaparmakov <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Jeff Mahoney <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Mikulas Patocka <[email protected]>
- Re: [PATCH] Use of getblk differs between locations
- From: Jeff Mahoney <[email protected]>
- [PATCH] Use of getblk differs between locations
- Prev by Date: Robust Futex update
- Next by Date: Re: [PATCH] Use of getblk differs between locations
- Previous by thread: Re: [PATCH] Use of getblk differs between locations
- Next by thread: Re: [PATCH] Use of getblk differs between locations
- Index(es):
 |