Linux NFS development
 help / color / mirror / Atom feed
From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	linux-nfs@vger.kernel.org, swise@opengridcomputing.com
Subject: Re: [PATCH 0/11] svcrdma: WR context management bug fixes and cleanup
Date: Thu, 29 May 2008 15:26:22 -0700	[thread overview]
Message-ID: <adaej7koigh.fsf@cisco.com> (raw)
In-Reply-To: <1212099937.22478.3.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org> (Tom Tucker's message of "Thu, 29 May 2008 17:25:37 -0500")

 > I'm inclined to say "no". But I'd like to hear if anyone out there is
 > dead in the water due to a bug in the 2.6.26 version.

To be honest I haven't had a chance to do much NFS/RDMA testing with the
current 2.6.26 tree.  But last I looked there were no major regressions
at least (still open issues I think, but definitely better than 2.6.25)

  parent reply	other threads:[~2008-05-29 22:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <12120836962076-git-send-email-tom@opengridcomputing.com>
2008-05-29 22:10 ` [PATCH 0/11] svcrdma: WR context management bug fixes and cleanup J. Bruce Fields
2008-05-29 22:25   ` Tom Tucker
     [not found]     ` <1212099937.22478.3.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-05-29 22:26       ` Roland Dreier [this message]
     [not found] ` <12120836962324-git-send-email-tom@opengridcomputing.com>
2008-06-16 19:48   ` [PATCH 01/11] svcrdma: Add a type for keeping NFS RPC mapping J. Bruce Fields
2008-06-21 16:31     ` Tom Tucker
2008-06-23 18:27       ` J. Bruce Fields
2008-06-24  2:58         ` Tom Tucker
2008-06-24 19:58           ` J. Bruce Fields
2008-06-24 20:31             ` Benny Halevy
2008-06-24 20:38             ` Trond Myklebust
     [not found]   ` <12120836963727-git-send-email-tom@opengridcomputing.com>
2008-06-16 21:04     ` [PATCH 02/11] svcrdma: Use RPC reply map for RDMA_WRITE processing J. Bruce Fields
2008-06-21 16:26       ` Tom Tucker
2008-06-23 18:21         ` J. Bruce Fields
2008-06-24  2:29           ` Tom Tucker
2008-06-21 16:51       ` Tom Tucker
2008-06-23 18:51         ` J. Bruce Fields
2008-06-24  3:02           ` Tom Tucker
     [not found]     ` <1212083697950-git-send-email-tom@opengridcomputing.com>
     [not found]       ` <1212083697236-git-send-email-tom@opengridcomputing.com>
     [not found]         ` <12120836973390-git-send-email-tom@opengridcomputing.com>
     [not found]           ` <12120836973638-git-send-email-tom@opengridcomputing.com>
     [not found]             ` <12120836973072-git-send-email-tom@opengridcomputing.com>
     [not found]               ` <12120836972503-git-send-email-tom@opengridcomputing.com>
     [not found]                 ` <12120836973166-git-send-email-tom@opengridcomputing.com>
     [not found]                   ` <12120836972648-git-send-email-tom@opengridcomputing.com>
2008-06-16 21:24                     ` [PATCH 10/11] svcrdma: Create a kmem cache for the WR contexts J. Bruce Fields
2008-06-21 17:08                       ` Tom Tucker

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=adaej7koigh.fsf@cisco.com \
    --to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=swise@opengridcomputing.com \
    --cc=tom@opengridcomputing.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