public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Dennis Dalessandro <dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 11/11] IB/mlx4: Prevent cross page boundary allocation
Date: Wed, 22 Jun 2016 11:01:42 -0400	[thread overview]
Message-ID: <20160622150141.GA25806@phlsvsds.ph.intel.com> (raw)
In-Reply-To: <1466605652-24798-12-git-send-email-leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>

On Wed, Jun 22, 2016 at 05:27:32PM +0300, Leon Romanovsky wrote:
>From: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
>
>Prevent cross page boundary allocation by allocating
>new page, this is required to be aligned with ConnectX-3 HW
>requirements.
>
>Not doing that might cause to "RDMA read local protection" error.
>
>Fixes: 1b2cd0fc673c ('IB/mlx4: Support the new memory registration API')
>Suggested-by: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
>Signed-off-by: Chuck Lever <chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
>Reviewed-by: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
>Signed-off-by: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>Signed-off-by: Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
>Signed-off-by: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

Hi Leon, why sign-off twice with different addresses?

-Denny
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-06-22 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 14:27 [PATCH rdma 00/11] IB core,mlx5,mlx4 fixes for 4.7-rc4 Leon Romanovsky
     [not found] ` <1466605652-24798-1-git-send-email-leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-06-22 14:27   ` [PATCH 01/11] IB/core: Fix no default GIDs when netdevice reregisters Leon Romanovsky
2016-06-22 14:27   ` [PATCH 02/11] IB/core: Fix RoCE v1 multicast join logic issue Leon Romanovsky
2016-06-22 14:27   ` [PATCH 03/11] IB/core: Fix false search of the IB_SA_WELL_KNOWN_GUID Leon Romanovsky
2016-06-22 14:27   ` [PATCH 04/11] IB/uverbs: Initialize ib_qp_init_attr with zeros Leon Romanovsky
2016-06-22 14:27   ` [PATCH 05/11] IB/mlx5: Fix post send fence logic Leon Romanovsky
2016-06-22 14:27   ` [PATCH 06/11] IB/mlx5: Fix wrong naming of port_rcv_data counter Leon Romanovsky
2016-06-22 14:27   ` [PATCH 07/11] IB/mlx4: Fix the SQ size of an RC QP Leon Romanovsky
2016-06-22 14:27   ` [PATCH 08/11] IB/mlx4: Fix error flow when sending mads under SRIOV Leon Romanovsky
2016-06-22 14:27   ` [PATCH 09/11] IB/mlx4: Check that port number is valid in flow steering create flow Leon Romanovsky
2016-06-22 14:27   ` [PATCH 10/11] IB/mlx4: Fix memory leak if QP creation failed Leon Romanovsky
2016-06-22 14:27   ` [PATCH 11/11] IB/mlx4: Prevent cross page boundary allocation Leon Romanovsky
     [not found]     ` <1466605652-24798-12-git-send-email-leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2016-06-22 15:01       ` Dennis Dalessandro [this message]
     [not found]         ` <20160622150141.GA25806-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2016-06-22 16:00           ` Leon Romanovsky
2016-06-23 14:11   ` [PATCH rdma 00/11] IB core,mlx5,mlx4 fixes for 4.7-rc4 Doug Ledford

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=20160622150141.GA25806@phlsvsds.ph.intel.com \
    --to=dennis.dalessandro-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=chuck.lever-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.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