Linux NFS development
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT] NFS client updates for 2.6.22...
Date: Thu, 03 May 2007 21:14:51 +0200	[thread overview]
Message-ID: <1178219691.24217.20.camel@twins> (raw)
In-Reply-To: <1178117571.5435.10.camel@heimdal.trondhjem.org>

On Wed, 2007-05-02 at 07:52 -0700, Trond Myklebust wrote:
> Hi Linus,
> 
> Please pull from the repository at
> 
>    git pull git://git.linux-nfs.org/pub/linux/nfs-2.6.git

I can confirm that this solves my missing IO completions problem; or at
least, my test has been running for 8h+ and still going strong, whereas
previous I would be lucky to get 1h.

Would it be reasonable to include the relevant patches in a
later .21-stable release?


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  parent reply	other threads:[~2007-05-03 19:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 14:52 [GIT] NFS client updates for 2.6.22 Trond Myklebust
2007-05-02 15:12 ` Tomasz Kłoczko
2007-05-04 12:39   ` Trond Myklebust
2007-05-03 19:14 ` Peter Zijlstra [this message]
2007-05-04 22:14   ` Trond Myklebust
2007-05-08  9:37 ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2007-07-11  3:44 Trond Myklebust

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=1178219691.24217.20.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.org \
    --cc=trond.myklebust@fys.uio.no \
    /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