On 4/3/16 5:29 AM, Shamir Rabinovitch wrote:
On Thu, Mar 31, 2016 at 04:02:46PM -0400, David Miller wrote:
From: shamir rabinovitch <shamir.rabinovi...@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.rabinovi...@oracle.com>
Reviewed-by: Wengang Wang <wen.gang.w...@oracle.com>
Reviewed-by: Ajaykumar Hotchandani <ajaykumar.hotchand...@oracle.com>
Acked-by: Santosh Shilimkar <santosh.shilim...@oracle.com>
Tested-by: Anand Bibhuti <anand.bibh...@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.
Thanks Shamir. Updated versions looks fine. You already
have my ack included.
Regards,
Santosh
