Re: [PATCH 11/12] NFS: Don't count O_DIRECT reads in the inode->i_dio_count

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 11/12] NFS: Don't count O_DIRECT reads in the inode->i_dio_count
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 15 Jun 2016 00:16:05 -0700
Cc: linux-nfs@xxxxxxxxxxxxxxx
In-reply-to: <1465931115-30784-11-git-send-email-trond.myklebust@primarydata.com>
References: <1465931115-30784-2-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-3-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-4-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-5-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-6-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-7-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-8-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-9-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-10-git-send-email-trond.myklebust@primarydata.com> <1465931115-30784-11-git-send-email-trond.myklebust@primarydata.com>
User-agent: Mutt/1.5.24 (2015-08-30)

Explanation of why reads are more special than writes here or in
general why they are safe?
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: [PATCH 11/12] NFS: Don't count O_DIRECT reads in the inode->i_dio_count
  - From: Trond Myklebust

References:
- [PATCH 02/12] NFS: Cache access checks more aggressively
  - From: Trond Myklebust
- [PATCH 03/12] NFS: Cache aggressively when file is open for writing
  - From: Trond Myklebust
- [PATCH 04/12] NFS: Kill NFS_INO_NFS_INO_FLUSHING: it is a performance killer
  - From: Trond Myklebust
- [PATCH 05/12] NFS: writepage of a single page should not be synchronous
  - From: Trond Myklebust
- [PATCH 06/12] NFS: Don't hold the inode lock across fsync()
  - From: Trond Myklebust
- [PATCH 07/12] NFS: Don't enable deep stack recursion when doing memory reclaim
  - From: Trond Myklebust
- [PATCH 08/12] NFS: Fix O_DIRECT verifier problems
  - From: Trond Myklebust
- [PATCH 09/12] NFS: Ensure we reset the write verifier 'committed' value on resend.
  - From: Trond Myklebust
- [PATCH 10/12] NFS: Do not serialise O_DIRECT reads and writes
  - From: Trond Myklebust
- [PATCH 11/12] NFS: Don't count O_DIRECT reads in the inode->i_dio_count
  - From: Trond Myklebust

Prev by Date: Re: [PATCH 10/12] NFS: Do not serialise O_DIRECT reads and writes
Next by Date: Re: [PATCH v2] nfsd: Always lock state exclusively.
Previous by thread: [PATCH 12/12] NFS: Clean up nfs_direct_complete()
Next by thread: Re: [PATCH 11/12] NFS: Don't count O_DIRECT reads in the inode->i_dio_count
Index(es):
- Date
- Thread

[Index of Archives] [Linux Filesystem Development] [Linux USB Development] [Linux Media Development] [Video for Linux] [Linux NILFS] [Linux Audio Users] [Yosemite Info] [Linux SCSI]