From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Weston Andros Adamson <dros@primarydata.com>,
linux-nfs list <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: [PATCH 0/2] RFC: Fix nfs_generic_pgio page vector issues
Date: Fri, 22 Aug 2014 21:48:17 +0200 [thread overview]
Message-ID: <53F79E81.4060509@gmx.de> (raw)
In-Reply-To: <BBF98A73-8235-4609-BB95-DC8C900E2134@primarydata.com>
On 08/15/2014 04:36 PM, Weston Andros Adamson wrote:
> This survived a full day of running trinity on one system and a full day of various iozone / fio on another.
>
> It’s good to go from my perspective.
>
> -dros
>
>
Test passed here too within 32 bit UML guests.
--
Toralf
prev parent reply other threads:[~2014-08-22 19:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 21:39 [PATCH 0/2] RFC: Fix nfs_generic_pgio page vector issues Weston Andros Adamson
2014-08-14 21:39 ` [PATCH 1/2] nfs: disallow duplicate pages in pgio page vectors Weston Andros Adamson
2014-08-14 21:39 ` [PATCH 2/2] nfs: can_coalesce_requests must enforce contiguity Weston Andros Adamson
2014-08-15 14:36 ` [PATCH 0/2] RFC: Fix nfs_generic_pgio page vector issues Weston Andros Adamson
2014-08-22 19:48 ` Toralf Förster [this message]
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=53F79E81.4060509@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=dros@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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;
as well as URLs for NNTP newsgroup(s).