Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1391569 > unrolled thread
| Started by | Or Gerlitz <gerlitz.or@gmail.com> |
|---|---|
| First post | 2016-04-30 06:40 +0200 |
| Last post | 2016-05-03 10:20 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH v5 09/21] IB/hns: Add hca support Or Gerlitz <gerlitz.or@gmail.com> - 2016-04-30 06:40 +0200
Re: [PATCH v5 09/21] IB/hns: Add hca support Or Gerlitz <gerlitz.or@gmail.com> - 2016-05-03 10:20 +0200
Re: [PATCH v5 09/21] IB/hns: Add hca support "Wei Hu (Xavier)" <xavier.huwei@huawei.com> - 2016-05-03 11:00 +0200
Re: [PATCH v5 09/21] IB/hns: Add hca support "Wei Hu (Xavier)" <xavier.huwei@huawei.com> - 2016-05-03 10:20 +0200
| From | Or Gerlitz <gerlitz.or@gmail.com> |
|---|---|
| Date | 2016-04-30 06:40 +0200 |
| Subject | Re: [PATCH v5 09/21] IB/hns: Add hca support |
| Message-ID | <rtuRb-1F8-1@gated-at.bofh.it> |
On Wed, Apr 27, 2016 at 6:34 AM, oulijun <oulijun@huawei.com> wrote: > On 2016/4/26 22:25, Jiri Pirko wrote: >> Tue, Apr 26, 2016 at 04:18:21PM CEST, leon@kernel.org wrote: >>>> I appreciate your keen eye. this code is meant for ARM64bit therefore should run corretly for 64-bit AARCH64. >> The driver should run correctly on any arch. > Hi Jiri Pirko, > Our driver run in ARM64 platform by depending on Kconfig. It will be configure in Kconfig file. Can you elaborate what design aspects in the driver or anywhere else should impose that limitation? Or.
[toc] | [next] | [standalone]
| From | Or Gerlitz <gerlitz.or@gmail.com> |
|---|---|
| Date | 2016-05-03 10:20 +0200 |
| Message-ID | <ruDIK-4pf-1@gated-at.bofh.it> |
| In reply to | #1391569 |
On Tue, May 3, 2016 at 10:57 AM, Wei Hu (Xavier) <xavier.huwei@huawei.com> wrote: > On 2016/4/30 12:33, Or Gerlitz wrote: >> Can you elaborate what design aspects in the driver or anywhere else >> should impose that limitation? > 1. Oulijun resolved the problem, and sent PATCH V6 on 2016-4-28. Thanks for > more comments. V6 still conditions things on ARM > 2. This driver for Hisilicon RoCE Engine run in ARM SoCs. > The Hisilicon Network Subsystem is a long term evolution IP which is > supposed to be used in Hisilicon ICT SoCs. HNS(Hisilicon Network Subsystem) > has a hardware support of performing RDMA with RoCE engine. I understand that the HW is targeted just for ARM environments. Is this the reason why you want to impose this build limitation or there's something in the driver design or code that is not going to work in other environments? > This Kconfig related with this driver as below: > > config INFINIBAND_HISILICON_HNS > tristate "Hisilicon Hns ROCE Driver" > depends on NET_VENDOR_HISILICON > depends on ARM64 && HNS && HNS_DSAF && HNS_ENET this is understood, my question came to better understand the limitations
[toc] | [prev] | [next] | [standalone]
| From | "Wei Hu (Xavier)" <xavier.huwei@huawei.com> |
|---|---|
| Date | 2016-05-03 11:00 +0200 |
| Message-ID | <ruEls-4O7-25@gated-at.bofh.it> |
| In reply to | #1393151 |
On 2016/5/3 16:14, Or Gerlitz wrote: > On Tue, May 3, 2016 at 10:57 AM, Wei Hu (Xavier) > <xavier.huwei@huawei.com> wrote: >> On 2016/4/30 12:33, Or Gerlitz wrote: > >>> Can you elaborate what design aspects in the driver or anywhere else >>> should impose that limitation? >> 1. Oulijun resolved the problem, and sent PATCH V6 on 2016-4-28. Thanks for >> more comments. > V6 still conditions things on ARM > > >> 2. This driver for Hisilicon RoCE Engine run in ARM SoCs. >> The Hisilicon Network Subsystem is a long term evolution IP which is >> supposed to be used in Hisilicon ICT SoCs. HNS(Hisilicon Network Subsystem) >> has a hardware support of performing RDMA with RoCE engine. > I understand that the HW is targeted just for ARM environments. Is > this the reason > why you want to impose this build limitation or there's something in > the driver design > or code that is not going to work in other environments? yes. Regards Wei Hu > >> This Kconfig related with this driver as below: >> >> config INFINIBAND_HISILICON_HNS >> tristate "Hisilicon Hns ROCE Driver" >> depends on NET_VENDOR_HISILICON >> depends on ARM64 && HNS && HNS_DSAF && HNS_ENET > this is understood, my question came to better understand the limitations > > . >
[toc] | [prev] | [next] | [standalone]
| From | "Wei Hu (Xavier)" <xavier.huwei@huawei.com> |
|---|---|
| Date | 2016-05-03 10:20 +0200 |
| Message-ID | <ruDIK-4pf-3@gated-at.bofh.it> |
| In reply to | #1391569 |
On 2016/4/30 12:33, Or Gerlitz wrote:
> On Wed, Apr 27, 2016 at 6:34 AM, oulijun <oulijun@huawei.com> wrote:
>> On 2016/4/26 22:25, Jiri Pirko wrote:
>>> Tue, Apr 26, 2016 at 04:18:21PM CEST, leon@kernel.org wrote:
>>>>> I appreciate your keen eye. this code is meant for ARM64bit therefore should run corretly for 64-bit AARCH64.
>>> The driver should run correctly on any arch.
>> Hi Jiri Pirko,
>> Our driver run in ARM64 platform by depending on Kconfig. It will be configure in Kconfig file.
> Can you elaborate what design aspects in the driver or anywhere else
> should impose that limitation?
>
> Or.
Hi, Or Gerlitz
1. Oulijun resloved the problem, and sent PATCH V6 on 2016-4-28. Thanks
for more comments.
2. This driver for Hisilicon RoCE Engine run in ARM SoCs.
The Hisilicon Network Subsystem is a long term evolution IP which is
supposed to be used in Hisilicon ICT SoCs. HNS(Hisilicon Network Subsystem)
has a hardware support of performing RDMA with RoCE engine.
This Kconfig related with this driver as below:
config INFINIBAND_HISILICON_HNS
tristate "Hisilicon Hns ROCE Driver"
depends on NET_VENDOR_HISILICON
depends on ARM64 && HNS && HNS_DSAF && HNS_ENET
Regards
Wei Hu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> .
>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web