netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: oulijun <oulijun@huawei.com>
To: Parav Pandit <pandit.parav@gmail.com>,
	"Wei Hu(Xavier)" <xavier.huwei@huawei.com>
Cc: Doug Ledford <dledford@redhat.com>,
	"Hefty, Sean" <sean.hefty@intel.com>, <hal.rosenstock@gmail.com>,
	<davem@davemloft.net>, <jeffrey.t.kirsher@intel.com>,
	<jiri@mellanox.com>, Or Gerlitz <ogerlitz@mellanox.com>,
	<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<netdev@vger.kernel.org>, <gongyangming@huawei.com>,
	<xiaokun@huawei.com>, <tangchaofei@huawei.com>,
	<haifeng.wei@huawei.com>, <yisen.zhuang@huawei.com>,
	<yankejian@huawei.com>, <lisheng011@huawei.com>,
	<charles.chenxin@huawei.com>, <linuxarm@huawei.com>
Subject: Re: [PATCH 3/4] infiniband: hns: add Hisilicon RoCE support(driver code)
Date: Mon, 14 Mar 2016 14:49:32 +0800	[thread overview]
Message-ID: <56E65EFC.3030109@huawei.com> (raw)
In-Reply-To: <CAG53R5WfQR1jJUOi1fjY=oEgsK_EAxkA9SiDPV_KHLHsmqg0BQ@mail.gmail.com>

Hi Parav Pandit, thanks your reviewing.
On 2016/3/4 17:37, Parav Pandit wrote:
> On Fri, Mar 4, 2016 at 2:11 PM, Wei Hu(Xavier) <xavier.huwei@huawei.com> wrote:
>> +
>> +int hns_roce_register_device(struct hns_roce_dev *hr_dev)
>> +{
>> +       int ret;
>> +       struct hns_roce_ib_iboe *iboe = NULL;
>> +       struct ib_device *ib_dev = NULL;
>> +       struct device *dev = &hr_dev->pdev->dev;
>> +
>> +       iboe = &hr_dev->iboe;
>> +
>> +       ib_dev = &hr_dev->ib_dev;
>> +       strlcpy(ib_dev->name, "hisi_%d", IB_DEVICE_NAME_MAX);
>> +
>> +       ib_dev->owner                   = THIS_MODULE;
>> +       ib_dev->node_type               = RDMA_NODE_IB_CA;
>> +       ib_dev->dma_device              = dev;
>> +
>> +       ib_dev->phys_port_cnt           = hr_dev->caps.num_ports;
>> +       ib_dev->local_dma_lkey          = hr_dev->caps.reserved_lkey;
>> +       ib_dev->num_comp_vectors        = hr_dev->caps.num_comp_vectors;
>> +       ib_dev->uverbs_abi_ver          = 1;
>> +       ib_dev->uverbs_cmd_mask         =
>> +               (1ULL << IB_USER_VERBS_CMD_GET_CONTEXT) |
>> +               (1ULL << IB_USER_VERBS_CMD_QUERY_DEVICE) |
>> +               (1ULL << IB_USER_VERBS_CMD_QUERY_PORT) |
>> +               (1ULL << IB_USER_VERBS_CMD_ALLOC_PD) |
>> +               (1ULL << IB_USER_VERBS_CMD_DEALLOC_PD) |
>> +               (1ULL << IB_USER_VERBS_CMD_REG_MR) |
>> +               (1ULL << IB_USER_VERBS_CMD_DEREG_MR) |
>> +               (1ULL << IB_USER_VERBS_CMD_CREATE_COMP_CHANNEL) |
>> +               (1ULL << IB_USER_VERBS_CMD_CREATE_CQ) |
>> +               (1ULL << IB_USER_VERBS_CMD_DESTROY_CQ) |
>> +               (1ULL << IB_USER_VERBS_CMD_CREATE_QP) |
>> +               (1ULL << IB_USER_VERBS_CMD_MODIFY_QP) |
>> +               (1ULL << IB_USER_VERBS_CMD_QUERY_QP) |
>> +               (1ULL << IB_USER_VERBS_CMD_DESTROY_QP);
>> +
> 
> Since SRQ is not supported in this driver version, can you keep
> remaining code base also to not bother about SRQ specifically
> poll_cq_one, modify_qp, destroy_qp etc?
> SRQ support can come as complete additional patch along with cmd_mask,
> callbacks and rest of the code.
> 
> .
Sorry, I see your review in time.
Sure, SRQ is not supported in current roce driver. I have verified the function
for RDMA. It is not influence. For your question, we need to analyse it scientific.
after that, i will reply your doubt, is that ok?

thanks
Lijun Ou

> 

  reply	other threads:[~2016-03-14  6:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  9:37 [PATCH 3/4] infiniband: hns: add Hisilicon RoCE support(driver code) Parav Pandit
2016-03-14  6:49 ` oulijun [this message]
2016-03-14 18:20   ` Parav Pandit
     [not found]     ` <CAG53R5UTc8xF4TdRJm3ASv6PQ-JxhW7vDgXpFtYqX2tz_58UeA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-19 11:28       ` oulijun
     [not found]         ` <56ED37C0.6090907-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-03-19 14:24           ` Parav Pandit
  -- strict thread matches above, loose matches on Subject: below --
2016-03-04  8:41 [PATCH 0/4] infiniband: hns: Hisilicon RoCE support Wei Hu(Xavier)
2016-03-04  8:41 ` [PATCH 3/4] infiniband: hns: add Hisilicon RoCE support(driver code) Wei Hu(Xavier)
2016-03-04  9:16   ` Jiri Pirko
     [not found]     ` <20160304091628.GB2150-6KJVSR23iU488b5SBfVpbw@public.gmane.org>
2016-03-09 11:18       ` oulijun
     [not found]         ` <56E0066E.1000106-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-03-09 11:25           ` Jiri Pirko

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=56E65EFC.3030109@huawei.com \
    --to=oulijun@huawei.com \
    --cc=charles.chenxin@huawei.com \
    --cc=davem@davemloft.net \
    --cc=dledford@redhat.com \
    --cc=gongyangming@huawei.com \
    --cc=haifeng.wei@huawei.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jiri@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=lisheng011@huawei.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=pandit.parav@gmail.com \
    --cc=sean.hefty@intel.com \
    --cc=tangchaofei@huawei.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xiaokun@huawei.com \
    --cc=yankejian@huawei.com \
    --cc=yisen.zhuang@huawei.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).