From: Shamir Rabinovitch <shamir.rabinovitch@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: rds-devel@oss.oracle.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2] rds: rds-stress show all zeros after few minutes
Date: Sun, 3 Apr 2016 15:29:52 +0300 [thread overview]
Message-ID: <20160403122951.GA14675@shamir-linux.uk.oracle.com> (raw)
In-Reply-To: <20160331.160246.2179579552166806534.davem@davemloft.net>
On Thu, Mar 31, 2016 at 04:02:46PM -0400, David Miller wrote:
> From: shamir rabinovitch <shamir.rabinovitch@oracle.com>
> Date: Thu, 31 Mar 2016 02:29:22 -0400
>
> > Issue can be seen on platforms that use 8K and above page size
> > while rds fragment size is 4K. On those platforms single page is
> > shared between 2 or more rds fragments. Each fragment has its own
> > offset and rds congestion map code need to take this offset to account.
> > Not taking this offset to account lead to reading the data fragment
> > as congestion map fragment and hang of the rds transmit due to far
> > congestion map corruption.
> >
> > Signed-off-by: shamir rabinovitch <shamir.rabinovitch@oracle.com>
> >
> > Reviewed-by: Wengang Wang <wen.gang.wang@oracle.com>
> > Reviewed-by: Ajaykumar Hotchandani <ajaykumar.hotchandani@oracle.com>
> > Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
> > Tested-by: Anand Bibhuti <anand.bibhuti@oracle.com>
>
> This doesn't apply cleanly to my current tree, please respin.
Sorry for the trouble.
Re-sent the patch based on net-next master.
Broke the patch according to comments from Santosh Shilimkar.
BR, Shamir
next prev parent reply other threads:[~2016-04-03 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 6:29 [PATCH v2] rds: rds-stress show all zeros after few minutes shamir rabinovitch
2016-03-31 20:02 ` David Miller
2016-04-03 12:29 ` Shamir Rabinovitch [this message]
2016-04-03 17:11 ` santosh.shilimkar
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=20160403122951.GA14675@shamir-linux.uk.oracle.com \
--to=shamir.rabinovitch@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.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).