Re: [PATCH 1/6] nfs: "open code" the NFS direct write rescheduler
- From: Andrew Morton <akpm@xxxxxxxx>
- Date: Fri, 19 May 2006 11:10:54 -0700
Chuck Lever <cel@xxxxxxxxxx> wrote:
+ * Prevent I/O completion while we're still rescheduling
+ */
+ dreq->outstanding++;
+
No locking.
dreq->count = 0;
+ list_for_each(pos, &dreq->rewrite_list) {
+ struct nfs_write_data *data =
+ list_entry(dreq->rewrite_list.next, struct nfs_write_data, pages);
+
+ spin_lock(&dreq->lock);
+ dreq->outstanding++;
+ spin_unlock(&dreq->lock);
Locking.
Deliberate?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 1/6] nfs: "open code" the NFS direct write rescheduler
- From: Chuck Lever
- Re: [PATCH 1/6] nfs: "open code" the NFS direct write rescheduler
- References:
- [PATCH 0/6] Support scatter/gather I/O in NFS direct I/O path
- From: Chuck Lever
- [PATCH 1/6] nfs: "open code" the NFS direct write rescheduler
- From: Chuck Lever
- [PATCH 0/6] Support scatter/gather I/O in NFS direct I/O path
- Prev by Date: [PATCH 4/6] nfs: alloc nfs_read/write_data as direct I/O is scheduled
- Next by Date: Re: [RFC][PATCH] MD RAID Acceleration: Move stripe operations outside the spin lock
- Previous by thread: [PATCH 1/6] nfs: "open code" the NFS direct write rescheduler
- Next by thread: Re: [PATCH 1/6] nfs: "open code" the NFS direct write rescheduler
- Index(es):
Relevant Pages
|
