public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: trond.myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/5] More short subjects for 2.6.34
Date: Mon, 01 Feb 2010 14:17:06 -0500	[thread overview]
Message-ID: <20100201191415.20189.39710.stgit@localhost.localdomain> (raw)

Here are some performance metric accounting fixes to consider for
2.6.34.  Also, a close(2) optimization for O_DIRECT files.

---

Chuck Lever (5):
      NFS: Make close(2) asynchronous when closing NFS O_DIRECT files
      NFS: Improve NFS iostat byte count accuracy for writes
      NFS: Account for NFS bytes read via the splice API
      NFS: Fix byte accounting for generic NFS reads
      NFS: Proper accounting for NFS VFS calls


 fs/nfs/file.c  |   30 ++++++++++++++++++++++--------
 fs/nfs/inode.c |    7 +------
 2 files changed, 23 insertions(+), 14 deletions(-)

-- 
Chuck Lever

             reply	other threads:[~2010-02-01 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01 19:17 Chuck Lever [this message]
     [not found] ` <20100201191415.20189.39710.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2010-02-01 19:17   ` [PATCH 1/5] NFS: Proper accounting for NFS VFS calls Chuck Lever
2010-02-01 19:17   ` [PATCH 2/5] NFS: Fix byte accounting for generic NFS reads Chuck Lever
2010-02-01 19:17   ` [PATCH 3/5] NFS: Account for NFS bytes read via the splice API Chuck Lever
2010-02-01 19:17   ` [PATCH 4/5] NFS: Improve NFS iostat byte count accuracy for writes Chuck Lever
2010-02-01 19:17   ` [PATCH 5/5] NFS: Make close(2) asynchronous when closing NFS O_DIRECT files Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100201191415.20189.39710.stgit@localhost.localdomain \
    --to=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@netapp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox