mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bob Pearson <rpearsonhpe@gmail.com>
To: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>,
	linux-rdma@vger.kernel.org, leonro@nvidia.com, jgg@nvidia.com,
	zyjzyj2000@gmail.com
Cc: linux-kernel@vger.kernel.org, yangx.jy@fujitsu.com,
	lizhijian@fujitsu.com, y-goto@fujitsu.com
Subject: Re: [PATCH for-next v5 3/7] RDMA/rxe: Move resp_states definition to rxe_verbs.h
Date: Thu, 18 May 2023 17:30:17 -0500	[thread overview]
Message-ID: <2d4f6023-0897-2414-45c0-e16b119dd9fb@gmail.com> (raw)
In-Reply-To: <a30a265438358d15068b6434795e00293a63fed5.1684397037.git.matsuda-daisuke@fujitsu.com>

On 5/18/23 03:21, Daisuke Matsuda wrote:
> To use the resp_states values in rxe_loc.h, it is necessary to move the
> definition to rxe_verbs.h, where other internal states of this driver are
> defined.
> 
> Signed-off-by: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
> ---
>  drivers/infiniband/sw/rxe/rxe.h       | 37 ---------------------------
>  drivers/infiniband/sw/rxe/rxe_verbs.h | 37 +++++++++++++++++++++++++++
>  2 files changed, 37 insertions(+), 37 deletions(-)
> 
> diff --git a/drivers/infiniband/sw/rxe/rxe.h b/drivers/infiniband/sw/rxe/rxe.h
> index d33dd6cf83d3..9b4d044a1264 100644
> --- a/drivers/infiniband/sw/rxe/rxe.h
> +++ b/drivers/infiniband/sw/rxe/rxe.h
> @@ -100,43 +100,6 @@
>  #define rxe_info_mw(mw, fmt, ...) ibdev_info_ratelimited((mw)->ibmw.device, \
>  		"mw#%d %s:  " fmt, (mw)->elem.index, __func__, ##__VA_ARGS__)
>  
> -/* responder states */
> -enum resp_states {
> -	RESPST_NONE,
> -	RESPST_GET_REQ,
> -	RESPST_CHK_PSN,
> -	RESPST_CHK_OP_SEQ,
> -	RESPST_CHK_OP_VALID,
> -	RESPST_CHK_RESOURCE,
> -	RESPST_CHK_LENGTH,
> -	RESPST_CHK_RKEY,
> -	RESPST_EXECUTE,
> -	RESPST_READ_REPLY,
> -	RESPST_ATOMIC_REPLY,
> -	RESPST_ATOMIC_WRITE_REPLY,
> -	RESPST_PROCESS_FLUSH,
> -	RESPST_COMPLETE,
> -	RESPST_ACKNOWLEDGE,
> -	RESPST_CLEANUP,
> -	RESPST_DUPLICATE_REQUEST,
> -	RESPST_ERR_MALFORMED_WQE,
> -	RESPST_ERR_UNSUPPORTED_OPCODE,
> -	RESPST_ERR_MISALIGNED_ATOMIC,
> -	RESPST_ERR_PSN_OUT_OF_SEQ,
> -	RESPST_ERR_MISSING_OPCODE_FIRST,
> -	RESPST_ERR_MISSING_OPCODE_LAST_C,
> -	RESPST_ERR_MISSING_OPCODE_LAST_D1E,
> -	RESPST_ERR_TOO_MANY_RDMA_ATM_REQ,
> -	RESPST_ERR_RNR,
> -	RESPST_ERR_RKEY_VIOLATION,
> -	RESPST_ERR_INVALIDATE_RKEY,
> -	RESPST_ERR_LENGTH,
> -	RESPST_ERR_CQ_OVERFLOW,
> -	RESPST_ERROR,
> -	RESPST_DONE,
> -	RESPST_EXIT,
> -};
> -
>  void rxe_set_mtu(struct rxe_dev *rxe, unsigned int dev_mtu);
>  
>  int rxe_add(struct rxe_dev *rxe, unsigned int mtu, const char *ibdev_name);
> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.h b/drivers/infiniband/sw/rxe/rxe_verbs.h
> index 26a20f088692..b6fbd9b3d086 100644
> --- a/drivers/infiniband/sw/rxe/rxe_verbs.h
> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.h
> @@ -127,6 +127,43 @@ struct rxe_comp_info {
>  	struct rxe_task		task;
>  };
>  
> +/* responder states */
> +enum resp_states {
> +	RESPST_NONE,
> +	RESPST_GET_REQ,
> +	RESPST_CHK_PSN,
> +	RESPST_CHK_OP_SEQ,
> +	RESPST_CHK_OP_VALID,
> +	RESPST_CHK_RESOURCE,
> +	RESPST_CHK_LENGTH,
> +	RESPST_CHK_RKEY,
> +	RESPST_EXECUTE,
> +	RESPST_READ_REPLY,
> +	RESPST_ATOMIC_REPLY,
> +	RESPST_ATOMIC_WRITE_REPLY,
> +	RESPST_PROCESS_FLUSH,
> +	RESPST_COMPLETE,
> +	RESPST_ACKNOWLEDGE,
> +	RESPST_CLEANUP,
> +	RESPST_DUPLICATE_REQUEST,
> +	RESPST_ERR_MALFORMED_WQE,
> +	RESPST_ERR_UNSUPPORTED_OPCODE,
> +	RESPST_ERR_MISALIGNED_ATOMIC,
> +	RESPST_ERR_PSN_OUT_OF_SEQ,
> +	RESPST_ERR_MISSING_OPCODE_FIRST,
> +	RESPST_ERR_MISSING_OPCODE_LAST_C,
> +	RESPST_ERR_MISSING_OPCODE_LAST_D1E,
> +	RESPST_ERR_TOO_MANY_RDMA_ATM_REQ,
> +	RESPST_ERR_RNR,
> +	RESPST_ERR_RKEY_VIOLATION,
> +	RESPST_ERR_INVALIDATE_RKEY,
> +	RESPST_ERR_LENGTH,
> +	RESPST_ERR_CQ_OVERFLOW,
> +	RESPST_ERROR,
> +	RESPST_DONE,
> +	RESPST_EXIT,
> +};
> +
>  enum rdatm_res_state {
>  	rdatm_res_state_next,
>  	rdatm_res_state_new,

Looks OK.

Reviewed-by: Bob Pearson <rpearsonhpe@gmail.com>


  reply	other threads:[~2023-05-18 22:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18  8:21 [PATCH for-next v5 0/7] On-Demand Paging on SoftRoCE Daisuke Matsuda
2023-05-18  8:21 ` [PATCH for-next v5 1/7] RDMA/rxe: Always defer tasks on responder and completer to workqueue Daisuke Matsuda
2023-05-18  8:26   ` Daisuke Matsuda (Fujitsu)
2023-05-18 22:25   ` Bob Pearson
2023-05-18  8:21 ` [PATCH for-next v5 2/7] RDMA/rxe: Make MR functions accessible from other rxe source code Daisuke Matsuda
2023-05-18 22:28   ` Bob Pearson
2023-05-18  8:21 ` [PATCH for-next v5 3/7] RDMA/rxe: Move resp_states definition to rxe_verbs.h Daisuke Matsuda
2023-05-18 22:30   ` Bob Pearson [this message]
2023-05-18  8:21 ` [PATCH for-next v5 4/7] RDMA/rxe: Add page invalidation support Daisuke Matsuda
2023-05-19 17:08   ` Bob Pearson
2023-05-18  8:21 ` [PATCH for-next v5 5/7] RDMA/rxe: Allow registering MRs for On-Demand Paging Daisuke Matsuda
2023-05-19 17:09   ` Bob Pearson
2023-06-12 16:18   ` Jason Gunthorpe
2023-07-19  6:00     ` Daisuke Matsuda (Fujitsu)
2023-07-21 18:46       ` Jason Gunthorpe
2023-05-18  8:21 ` [PATCH for-next v5 6/7] RDMA/rxe: Add support for Send/Recv/Write/Read with ODP Daisuke Matsuda
2023-05-19 17:10   ` Bob Pearson
2023-05-19 17:10   ` Bob Pearson
2023-06-12 16:22   ` Jason Gunthorpe
2023-07-19  6:01     ` Daisuke Matsuda (Fujitsu)
2023-09-08  6:35     ` Daisuke Matsuda (Fujitsu)
2023-09-08 13:14       ` Jason Gunthorpe
2023-05-18  8:21 ` [PATCH for-next v5 7/7] RDMA/rxe: Add support for the traditional Atomic operations " Daisuke Matsuda
2023-05-22 18:49   ` Bob Pearson
2023-05-19  6:41 ` [PATCH for-next v5 0/7] On-Demand Paging on SoftRoCE Guoqing Jiang
2023-05-19  9:57   ` Daisuke Matsuda (Fujitsu)
2023-05-19 10:20     ` Guoqing Jiang

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=2d4f6023-0897-2414-45c0-e16b119dd9fb@gmail.com \
    --to=rpearsonhpe@gmail.com \
    --cc=jgg@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lizhijian@fujitsu.com \
    --cc=matsuda-daisuke@fujitsu.com \
    --cc=y-goto@fujitsu.com \
    --cc=yangx.jy@fujitsu.com \
    --cc=zyjzyj2000@gmail.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

Powered by JetHome