From: "Steve Wise" <swise@opengridcomputing.com>
To: <bfields@fieldses.org>
Cc: <linux-rdma@vger.kernel.org>, <linux-nfs@vger.kernel.org>, <tom@ogc.us>
Subject: RE: [PATCH] svcrdma: send_write() must not overflow the device's max sge
Date: Thu, 10 Jul 2014 14:51:16 -0500 [thread overview]
Message-ID: <005d01cf9c78$4fa621d0$eef26570$@opengridcomputing.com> (raw)
In-Reply-To: <20140709184914.22217.59770.stgit@build.ogc.int>
I tested this with nfsv3 and v4, over cxgb4 and mlx4: cthon04, iozone, fio, and xfs. No regressions seen...
Steve.
WARNING: multiple messages have this Message-ID (diff)
From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tom-/Yg/VP3ZvrM@public.gmane.org
Subject: RE: [PATCH] svcrdma: send_write() must not overflow the device's max sge
Date: Thu, 10 Jul 2014 14:51:16 -0500 [thread overview]
Message-ID: <005d01cf9c78$4fa621d0$eef26570$@opengridcomputing.com> (raw)
In-Reply-To: <20140709184914.22217.59770.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
I tested this with nfsv3 and v4, over cxgb4 and mlx4: cthon04, iozone, fio, and xfs. No regressions seen...
Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-10 19:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 18:49 [PATCH] svcrdma: send_write() must not overflow the device's max sge Steve Wise
2014-07-09 18:49 ` Steve Wise
2014-07-10 19:51 ` Steve Wise [this message]
2014-07-10 19:51 ` Steve Wise
2014-07-10 20:17 ` J. Bruce Fields
2014-07-10 20:17 ` J. Bruce Fields
2014-07-16 6:16 ` Devesh Sharma
2014-07-16 6:16 ` Devesh Sharma
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='005d01cf9c78$4fa621d0$eef26570$@opengridcomputing.com' \
--to=swise@opengridcomputing.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tom@ogc.us \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.