From: Trond Myklebust <trondmy@hammerspace.com>
To: "chuck.lever@oracle.com" <chuck.lever@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] SUNRPC: Remove rpc_xprt::tsh_size
Date: Thu, 3 Jan 2019 21:28:06 +0000 [thread overview]
Message-ID: <076cce85045dbaab3ca40947b2599f96cff66b53.camel@hammerspace.com> (raw)
In-Reply-To: <791EE189-59E5-4D58-9CF6-6D2CFC6C1210@oracle.com>
On Thu, 2019-01-03 at 16:07 -0500, Chuck Lever wrote:
> > On Jan 3, 2019, at 3:53 PM, Chuck Lever <chuck.lever@oracle.com>
> > wrote:
> >
> > > On Jan 3, 2019, at 1:47 PM, Trond Myklebust <
> > > trondmy@hammerspace.com> wrote:
> > >
> > > On Thu, 2019-01-03 at 13:29 -0500, Chuck Lever wrote:
> > > > + reclen = req->rq_snd_buf.len;
> > > > + marker = cpu_to_be32(RPC_LAST_STREAM_FRAGMENT |
> > > > reclen);
> > > > + return kernel_sendmsg(transport->sock, &msg, &iov, 1,
> > > > iov.iov_len);
> > >
> > > So what does this do for performance? I'd expect that adding
> > > another
> > > dive into the socket layer will come with penalties.
> >
> > NFSv3 on TCP, sec=sys, 56Gbs IBoIP, v4.20 + my v4.21 patches
> > fio, 8KB random, 70% read, 30% write, 16 threads, iodepth=16
> >
> > Without this patch:
> >
> > read: IOPS=28.7k, BW=224MiB/s (235MB/s)(11.2GiB/51092msec)
> > write: IOPS=12.3k, BW=96.3MiB/s (101MB/s)(4918MiB/51092msec)
> >
> > With this patch:
> >
> > read: IOPS=28.6k, BW=224MiB/s (235MB/s)(11.2GiB/51276msec)
> > write: IOPS=12.3k, BW=95.8MiB/s (100MB/s)(4914MiB/51276msec)
> >
> > Seems like that's in the noise.
>
> Sigh. That's because it was the same kernel. Again, with feeling:
>
> 4.20.0-rc7-00048-g9274254:
> read: IOPS=28.6k, BW=224MiB/s (235MB/s)(11.2GiB/51276msec)
> write: IOPS=12.3k, BW=95.8MiB/s (100MB/s)(4914MiB/51276msec)
>
> 4.20.0-rc7-00049-ga4dea15:
> read: IOPS=27.2k, BW=212MiB/s (223MB/s)(11.2GiB/53979msec)
> write: IOPS=11.7k, BW=91.1MiB/s (95.5MB/s)(4917MiB/53979msec)
>
So about a 5% reduction in performance?
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2019-01-03 21:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-03 18:29 [PATCH] SUNRPC: Remove rpc_xprt::tsh_size Chuck Lever
2019-01-03 18:47 ` Trond Myklebust
2019-01-03 20:53 ` Chuck Lever
2019-01-03 21:07 ` Chuck Lever
2019-01-03 21:28 ` Trond Myklebust [this message]
2019-01-03 21:35 ` Chuck Lever
2019-01-03 22:49 ` Chuck Lever
2019-01-04 4:00 ` Trond Myklebust
2019-01-04 21:35 ` Chuck Lever
2019-01-04 22:44 ` Trond Myklebust
2019-01-10 17:13 ` 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=076cce85045dbaab3ca40947b2599f96cff66b53.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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).