netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Konstantin Taranov <kotaranov@linux.microsoft.com>
Cc: kotaranov@microsoft.com, pabeni@redhat.com,
	haiyangz@microsoft.com, kys@microsoft.com, edumazet@google.com,
	kuba@kernel.org, davem@davemloft.net, decui@microsoft.com,
	wei.liu@kernel.org, longli@microsoft.com, jgg@ziepe.ca,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH rdma-next 3/3] RDMA/mana_ib: Add support of 4M, 1G, and 2G pages
Date: Wed, 9 Apr 2025 15:27:43 +0300	[thread overview]
Message-ID: <20250409122743.GK199604@unreal> (raw)
In-Reply-To: <1743777955-2316-4-git-send-email-kotaranov@linux.microsoft.com>

On Fri, Apr 04, 2025 at 07:45:55AM -0700, Konstantin Taranov wrote:
> From: Konstantin Taranov <kotaranov@microsoft.com>
> 
> Check PF capability flag whether the 4M, 1G, and 2G pages are
> supported. Add these pages sizes to mana_ib, if supported.
> 
> Define possible page sizes in enum gdma_page_type and
> remove unused enum atb_page_size.
> 
> Signed-off-by: Konstantin Taranov <kotaranov@microsoft.com>
> ---
>  drivers/infiniband/hw/mana/main.c             | 10 +++++--
>  drivers/infiniband/hw/mana/mana_ib.h          |  1 +
>  .../net/ethernet/microsoft/mana/gdma_main.c   |  1 +
>  include/net/mana/gdma.h                       | 30 ++++++++++---------
>  4 files changed, 25 insertions(+), 17 deletions(-)

<...>

>  enum gdma_page_type {
>  	GDMA_PAGE_TYPE_4K,
> +	GDMA_PAGE_SIZE_8K,
> +	GDMA_PAGE_SIZE_16K,
> +	GDMA_PAGE_SIZE_32K,
> +	GDMA_PAGE_SIZE_64K,
> +	GDMA_PAGE_SIZE_128K,
> +	GDMA_PAGE_SIZE_256K,
> +	GDMA_PAGE_SIZE_512K,
> +	GDMA_PAGE_SIZE_1M,
> +	GDMA_PAGE_SIZE_2M,
> +	/* Only when GDMA_DRV_CAP_FLAG_1_GDMA_PAGES_4MB_1GB_2GB is set */
> +	GDMA_PAGE_SIZE_4M,
> +	GDMA_PAGE_SIZE_1G = 18,
> +	GDMA_PAGE_SIZE_2G

Where are all these defines used?

Thanks

  reply	other threads:[~2025-04-09 12:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 14:45 [PATCH rdma-next 0/3] RDMA/mana_ib: extend MR support Konstantin Taranov
2025-04-04 14:45 ` [PATCH rdma-next 1/3] RDMA/mana_ib: Access remote atomic for MRs Konstantin Taranov
2025-04-09 12:28   ` Leon Romanovsky
2025-04-10 13:37     ` [EXTERNAL] " Konstantin Taranov
2025-04-10 13:54       ` Leon Romanovsky
2025-04-14  9:15         ` Konstantin Taranov
2025-04-04 14:45 ` [PATCH rdma-next 2/3] RDMA/mana_ib: support of the zero based MRs Konstantin Taranov
2025-04-04 14:45 ` [PATCH rdma-next 3/3] RDMA/mana_ib: Add support of 4M, 1G, and 2G pages Konstantin Taranov
2025-04-09 12:27   ` Leon Romanovsky [this message]
2025-04-10 13:38     ` [EXTERNAL] " Konstantin Taranov
2025-04-10 13:55       ` Leon Romanovsky

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=20250409122743.GK199604@unreal \
    --to=leon@kernel.org \
    --cc=davem@davemloft.net \
    --cc=decui@microsoft.com \
    --cc=edumazet@google.com \
    --cc=haiyangz@microsoft.com \
    --cc=jgg@ziepe.ca \
    --cc=kotaranov@linux.microsoft.com \
    --cc=kotaranov@microsoft.com \
    --cc=kuba@kernel.org \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=longli@microsoft.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wei.liu@kernel.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;
as well as URLs for NNTP newsgroup(s).