From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: Zhu Yanjun <yanjun.zhu@oracle.com>,
davem@davemloft.net, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 1/1] net: rds: exchange of 8K and 1M pool
Date: Wed, 24 Apr 2019 09:59:42 -0700 [thread overview]
Message-ID: <b005573c-1dfe-649d-dcc3-c5e72c82d22c@oracle.com> (raw)
In-Reply-To: <20190424065642.28630-1-yanjun.zhu@oracle.com>
On 4/23/2019 11:56 PM, Zhu Yanjun wrote:
> Before the commit 490ea5967b0d ("RDS: IB: move FMR code to its own file"),
> when the dirty_count is greater than 9/10 of max_items of 8K pool,
> 1M pool is used, Vice versa. After the commit 490ea5967b0d ("RDS: IB: move
> FMR code to its own file"), the above is removed. When we make the
> following tests.
>
> Server:
> rds-stress -r 1.1.1.16 -D 1M
>
> Client:
> rds-stress -r 1.1.1.14 -s 1.1.1.16 -D 1M
>
> The following will appear.
> "
> connecting to 1.1.1.16:4000
> negotiated options, tasks will start in 2 seconds
> Starting up..header from 1.1.1.166:4001 to id 4001 bogus
> ..
> tsks tx/s rx/s tx+rx K/s mbi K/s mbo K/s tx us/c rtt us
> cpu %
> 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00
> 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00
> 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00
> 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00
> 1 0 0 0.00 0.00 0.00 0.00 0.00 -1.00
> ...
> "
> So this exchange between 8K and 1M pool is added back.
>
> Fixes: commit 490ea5967b0d ("RDS: IB: move FMR code to its own file")
> Signed-off-by: Zhu Yanjun <yanjun.zhu@oracle.com>
> ---
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
next prev parent reply other threads:[~2019-04-24 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 6:56 [PATCH 1/1] net: rds: exchange of 8K and 1M pool Zhu Yanjun
2019-04-24 16:59 ` Santosh Shilimkar [this message]
2019-04-24 19:08 ` David Miller
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=b005573c-1dfe-649d-dcc3-c5e72c82d22c@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yanjun.zhu@oracle.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).