2019-05-19 05:07:45 -07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2021-11-01 00:39:12 -07:00
|
|
|
ccflags-y += -I$(src)
|
2017-01-09 08:55:13 -07:00
|
|
|
obj-$(CONFIG_SMC) += smc.o
|
2017-01-09 08:55:26 -07:00
|
|
|
obj-$(CONFIG_SMC_DIAG) += smc_diag.o
|
2017-01-09 08:55:21 -07:00
|
|
|
smc-y := af_smc.o smc_pnet.o smc_ib.o smc_clc.o smc_core.o smc_wr.o smc_llc.o
|
2021-06-16 07:52:55 -07:00
|
|
|
smc-y += smc_cdc.o smc_tx.o smc_rx.o smc_close.o smc_ism.o smc_netlink.o smc_stats.o
|
net/smc: Introduce IPPROTO_SMC
This patch allows to create smc socket via AF_INET,
similar to the following code,
/* create v4 smc sock */
v4 = socket(AF_INET, SOCK_STREAM, IPPROTO_SMC);
/* create v6 smc sock */
v6 = socket(AF_INET6, SOCK_STREAM, IPPROTO_SMC);
There are several reasons why we believe it is appropriate here:
1. For smc sockets, it actually use IPv4 (AF-INET) or IPv6 (AF-INET6)
address. There is no AF_SMC address at all.
2. Create smc socket in the AF_INET(6) path, which allows us to reuse
the infrastructure of AF_INET(6) path, such as common ebpf hooks.
Otherwise, smc have to implement it again in AF_SMC path.
Signed-off-by: D. Wythe <alibuda@linux.alibaba.com>
Reviewed-by: Wenjia Zhang <wenjia@linux.ibm.com>
Reviewed-by: Dust Li <dust.li@linux.alibaba.com>
Tested-by: Niklas Schnelle <schnelle@linux.ibm.com>
Tested-by: Wenjia Zhang <wenjia@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2024-06-13 11:00:30 -07:00
|
|
|
smc-y += smc_tracepoint.o smc_inet.o
|
2022-03-06 18:54:24 -07:00
|
|
|
smc-$(CONFIG_SYSCTL) += smc_sysctl.o
|
2024-04-27 23:07:29 -07:00
|
|
|
smc-$(CONFIG_SMC_LO) += smc_loopback.o
|
