RE: A question for connection management with vlan device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: oulijun [mailto:oulijun@xxxxxxxxxx]
> Sent: Tuesday, April 17, 2018 3:15 AM
> To: Parav Pandit <parav@xxxxxxxxxxxx>; linux-rdma <linux-
> rdma@xxxxxxxxxxxxxxx>
> Cc: Linuxarm <linuxarm@xxxxxxxxxx>
> Subject: Re: 【Ask for help】A question for connection management with vlan
> device
> 
> 在 2018/4/16 22:03, Parav Pandit 写道:
> > Hi,
> >
> >> -----Original Message-----
> >> From: linux-rdma-owner@xxxxxxxxxxxxxxx [mailto:linux-rdma-
> >> owner@xxxxxxxxxxxxxxx] On Behalf Of oulijun
> >> Sent: Monday, April 16, 2018 2:19 AM
> >> To: linux-rdma <linux-rdma@xxxxxxxxxxxxxxx>
> >> Cc: Linuxarm <linuxarm@xxxxxxxxxx>
> >> Subject: 【Ask for help】A question for connection management with vlan
> >> device
> >>
> >> Hi,All
> >>    I am developing the cm for vlan device. I have a question need to
> >> help from you.
> > Cm for vlan device is support for IPv4 addresses.
> > Did it fail for you? If so, which client-server test commands did you try?
> >
> Yes, The test flow as follows:
> 1. I configure the vlan device ip;
>    ifconfig eth0 192.168.1.100;
>    vconfig add eth0 100;
>    ifconfig eth0.100 192.168.1.1
> 
Both the interfaces are in same subnet. There isn't good way to pick whether to use vlan or not.
Please have them in different subnet and it should work.
Such as 193.168.1.1

> root@(none)# ifconfig
> eth0      Link encap:Ethernet  HWaddr A2:AF:57:53:A5:39
>           inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::a0af:57ff:fe53:a539/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:1732 (1.6 KiB)
> 
> eth0.100  Link encap:Ethernet  HWaddr A2:AF:57:53:A5:39
>           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
>           inet6 addr: fe80::a0af:57ff:fe53:a539/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:866 (866.0 B)
> 
> 2. I use perftest tool, the cmd as follows:
>    server: ./ib_send_bw -n 5 -x 4 -R
>    client: ./ib_send_bw -n 5 -x 4 -R 192.168.1.1
> 
>    I also check the gid_attr, the info as follows:
>    root@(none)# cat /sys/class/infiniband/hns_0/ports/1/gid_attrs/types/4
> IB/RoCE v1
> 
> root@(none)# cat /sys/class/infiniband/hns_0/ports/1/gid_attrs/ndevs/4
> eth0.100
> 

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




[Index of Archives]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Yosemite Photos]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux