- High-performance-network - mailweb.openeuler.org

Re: 关于欧拉社区合入rdma-core PR时门禁系统构建问题
by li.fuyan＠zte.com.cn 03 Sep '24

03 Sep '24

你好，帮忙看一下如下构建信息，我从日志里看不出来是哪里有问题，需要你的帮助。 PR链接: https://gitee.com/src-openeuler/rdma-core/pulls/165 构建链接： https://openeulerjenkins.osinfra.cn/job/multiarch/job/src-openeuler/job/x86… 构建错误日志： 3771 2024-09-03 17:22:56 patching file redhat/rdma-core.spec 3772 2024-09-03 17:22:56 Hunk #1 succeeded at 176 (offset 2 lines). 3773 2024-09-03 17:22:56 Hunk #2 succeeded at 204 (offset 2 lines). 3774 2024-09-03 17:22:56 Hunk #3 succeeded at 586 (offset 3 lines). 3775 2024-09-03 17:22:56 error: Bad exit status from /var/tmp/rpm-tmp.43Oe9Z (%prep) 3776 2024-09-03 17:22:56 Bad exit status from /var/tmp/rpm-tmp.43Oe9Z (%prep) 3777 2024-09-03 17:22:56 3778 2024-09-03 17:22:56 RPM build errors: 3779 2024-09-03 17:22:56 failed to build rpms with rdma-core.spec 看起来像是redhat/rdma-core.spec文件有异常，但是从如下修改内容来看，没有看到明显的错误，请帮忙看一下。李富艳软件开发工程师 ICF六部/智算云底座研发中心/无线及算力研究院 ICF Dept. VI/Intelligent Computing and Cloud Foundation R&D Center/Wireless and Computing Product R&D Institute 中兴通讯股份有限公司西安市长安区西沣路五星段9号中兴通讯1E-401 邮编: 710114 T: +86 029 xxxxxxxx M: +86 15332482266 E: li.fuyan(a)zte.com.cn www.zte.com.cn Original From: 李富艳00122684 To: tangchengchang <tangchengchang(a)huawei.com>;chenshaowei3(a)h-partners.com <chenshaowei3(a)h-partners.com>;wanghuan158(a)h-partners.com <wanghuan158(a)h-partners.com>; Cc: wanghuan158(a)h-partners.com <wanghuan158(a)h-partners.com>; Date: 2024年08月31日 14:07 Subject: 关于欧拉社区合入PR时门禁系统构建问题 tangchegnchang 你好，已经根据你之前提交的评审意见修改了ZTE Dinghai rdma-core的代码，但是由于操作问题，修改后的代码提交了新的PR，链接如下： https://gitee.com/src-openeuler/rdma-core/pulls/165 门禁系统当前状态为check_build失败，查看build日志，我发现提示信息如下红色标记，changelog部分错误看起来是基础内容，不是本次合入的，请你帮忙看一下如何解决这种问题。 https://eulermaker.compass-ci.openeuler.openatom.cn/package/build-record?os… 2024-08-31 12:59:19 Hunk #1 succeeded at 245 (offset 5 lines). 3772 2024-08-31 12:59:19 3773 2024-08-31 12:59:19 RPM build errors: 3774 2024-08-31 12:59:19 error: Bad exit status from /var/tmp/rpm-tmp.ikn0I8 (%prep) 3775 2024-08-31 12:59:19 bad date in %changelog: Wed May 29 zhangyaqi <zhangyaqi(a)kylinos.cn> - 50.0-11 3776 2024-08-31 12:59:19 Bad exit status from /var/tmp/rpm-tmp.ikn0I8 (%prep) 3777 2024-08-31 12:59:19 failed to build rpms with rdma-core.spec 另外，能否麻烦你加我微信或者你提供下你的电话，方便后续沟通。我的电话：15332482266 我的微信二维码如下，方便的话请你加一下我李富艳软件开发工程师 ICF六部/智算云底座研发中心/无线及算力研究院 ICF Dept. VI/Intelligent Computing and Cloud Foundation R&D Center/Wireless and Computing Product R&D Institute 中兴通讯股份有限公司西安市长安区西沣路五星段9号中兴通讯1E-401 邮编: 710114 T: +86 029 xxxxxxxx M: +86 15332482266 E: li.fuyan(a)zte.com.cn www.zte.com.cn

1 0

Perftest: Fix failure in creating cq when create_cq_ex is not supported by providers
by Junxian Huang 30 Aug '24

30 Aug '24

The previous TD lock-free patch introduced ibv_create_cq_ex() to perftest, but it breaks the provider devices which do not support this API yet. For these devices calling this API leads to an errno of EOPNOTSUPP. So add a check of errno, and if it is EOPNOTSUPP, use ibv_create_cq() as a fallback. Fixes: b6f957f6bc6c ("Perftest: Add support for TD lock-free mode") Signed-off-by: Junxian Huang <huangjunxian6(a)hisilicon.com> --- src/perftest_resources.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/perftest_resources.c b/src/perftest_resources.c index 2653207..814ffdb 100755 --- a/src/perftest_resources.c +++ b/src/perftest_resources.c @@ -1547,6 +1547,8 @@ int create_reg_cqs(struct pingpong_context *ctx, #endif ctx->send_cq = ibv_cq_ex_to_cq(ibv_create_cq_ex(ctx->context, &send_cq_attr)); if (!ctx->send_cq) { + if (!user_param->no_lock && errno == EOPNOTSUPP) + goto cq_ex_not_supported; fprintf(stderr, "Couldn't create CQ\n"); return FAILURE; } @@ -1571,7 +1573,9 @@ int create_reg_cqs(struct pingpong_context *ctx, } } return SUCCESS; -#else + +cq_ex_not_supported: +#endif ctx->send_cq = ibv_create_cq(ctx->context,tx_buffer_depth * user_param->num_of_qps, NULL, ctx->send_channel, user_param->eq_num); if (!ctx->send_cq) { @@ -1589,7 +1593,6 @@ int create_reg_cqs(struct pingpong_context *ctx, } return SUCCESS; -#endif } /****************************************************************************** -- 2.33.0

1 0

Perftest: Fix TD lock-free mode not working for QP
by Junxian Huang 19 Aug '24

19 Aug '24

From: Guofeng Yue <yueguofeng(a)h-partners.com> When creating QP in TD lock-free mode, set attr_ex.pd with ctx->pad instead of ctx->pd, otherwise the lock-free won't work. Fixes: 38d9fcfc3580 ("Perftest: Add support for TD lock-free mode") Signed-off-by: Guofeng Yue <yueguofeng(a)h-partners.com> Signed-off-by: Junxian Huang <huangjunxian6(a)hisilicon.com> --- src/perftest_resources.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/perftest_resources.c b/src/perftest_resources.c index 40b7ddf..2ea07fb 100755 --- a/src/perftest_resources.c +++ b/src/perftest_resources.c @@ -2384,7 +2384,13 @@ struct ibv_qp* ctx_qp_create(struct pingpong_context *ctx, else if (opcode == IBV_WR_RDMA_READ) attr_ex.send_ops_flags |= IBV_QP_EX_WITH_RDMA_READ; } + + #ifdef HAVE_TD_API + attr_ex.pd = user_param->no_lock ? ctx->pad : ctx->pd; + #else attr_ex.pd = ctx->pd; + #endif + attr_ex.comp_mask |= IBV_QP_INIT_ATTR_SEND_OPS_FLAGS | IBV_QP_INIT_ATTR_PD; attr_ex.send_cq = attr.send_cq; attr_ex.recv_cq = attr.recv_cq; -- 2.33.0

1 0

[PATCH Perftest v3] Perftest: Add support for TD lock-free mode
by Junxian Huang 13 Aug '24

13 Aug '24

From: Guofeng Yue <yueguofeng(a)h-partners.com> Add support for TD lock-free mode New option: --no_lock Usage example: ./ib_send_bw -d hns_0 --no_lock ./ib_send_bw -d hns_0 --no_lock 192.168.100.100 Signed-off-by: Guofeng Yue <yueguofeng(a)h-partners.com> --- configure.ac | 14 ++++++ src/perftest_parameters.c | 31 +++++++++++++- src/perftest_parameters.h | 1 + src/perftest_resources.c | 90 +++++++++++++++++++++++++++++++++++++++ src/perftest_resources.h | 4 ++ 5 files changed, 138 insertions(+), 2 deletions(-) diff --git a/configure.ac b/configure.ac index e59bf39..862eb08 100755 --- a/configure.ac +++ b/configure.ac @@ -389,6 +389,20 @@ if [test $HAVE_HNSDV = yes]; then AC_SUBST([LIBHNS]) fi +AC_TRY_LINK([#include <infiniband/verbs.h>], + [ibv_cq_ex_to_cq], [HAVE_CQ_EX=yes], [HAVE_CQ_EX=no]) +AM_CONDITIONAL([HAVE_CQ_EX], [test "x$HAVE_CQ_EX" = "xyes"]) +if [test $HAVE_CQ_EX = yes]; then + AC_DEFINE([HAVE_CQ_EX], [1], [Have CQ EX APT support]) +fi + +AC_TRY_LINK([#include <infiniband/verbs.h>], + [ibv_alloc_td], [HAVE_TD_API=yes], [HAVE_TD_API=no]) +AM_CONDITIONAL([HAVE_TD_API], [test "x$HAVE_TD_API" = "xyes"]) +if [test $HAVE_TD_API = yes]; then + AC_DEFINE([HAVE_TD_API], [1], [Have TD API support]) +fi + CFLAGS="-g -Wall -D_GNU_SOURCE -O3 $CFLAGS" LDFLAGS="$LDFLAGS" LIBS=$LIBS" -lpthread" diff --git a/src/perftest_parameters.c b/src/perftest_parameters.c index ff34a2c..c6608b7 100755 --- a/src/perftest_parameters.c +++ b/src/perftest_parameters.c @@ -466,6 +466,11 @@ static void usage(const char *argv0, VerbType verb, TestType tst, int connection printf(" Use a Shared Receive Queue. --rx-depth controls max-wr size of the SRQ \n"); } + #ifdef HAVE_TD_API + printf(" --no_lock "); + printf(" No lock in IO, include post send, post recv, post srq recv, poll cq \n"); + #endif + if (connection_type != RawEth) { printf(" --ipv6 "); printf(" Use IPv6 GID. Default is IPv4\n"); @@ -872,6 +877,7 @@ static void init_perftest_params(struct perftest_parameters *user_param) user_param->has_source_ip = 0; user_param->use_write_with_imm = 0; user_param->congest_type = OFF; + user_param->no_lock = OFF; } static int open_file_write(const char* file_path) @@ -2322,6 +2328,9 @@ int parser(struct perftest_parameters *user_param,char *argv[], int argc) #ifdef HAVE_HNSDV static int congest_type_flag = 0; #endif + #ifdef HAVE_TD_API + static int no_lock_flag = 0; + #endif char *server_ip = NULL; char *client_ip = NULL; @@ -2401,6 +2410,9 @@ int parser(struct perftest_parameters *user_param,char *argv[], int argc) { .name = "run_infinitely", .has_arg = 0, .flag = &run_inf_flag, .val = 1 }, { .name = "report_gbits", .has_arg = 0, .flag = &report_fmt_flag, .val = 1}, { .name = "use-srq", .has_arg = 0, .flag = &srq_flag, .val = 1}, + #ifdef HAVE_TD_API + { .name = "no_lock", .has_arg = 0, .flag = &no_lock_flag, .val = 1}, + #endif { .name = "use-null-mr", .has_arg = 0, .flag = &use_null_mr_flag, .val = 1}, { .name = "report-both", .has_arg = 0, .flag = &report_both_flag, .val = 1}, { .name = "reversed", .has_arg = 0, .flag = &is_reversed_flag, .val = 1}, @@ -3144,6 +3156,12 @@ int parser(struct perftest_parameters *user_param,char *argv[], int argc) user_param->use_srq = 1; } + #ifdef HAVE_TD_API + if (no_lock_flag) { + user_param->no_lock = 1; + } + #endif + if (use_null_mr_flag) { user_param->use_null_mr = 1; } @@ -3488,15 +3506,24 @@ void ctx_print_test_info(struct perftest_parameters *user_param) printf(" Number of qps : %d\t\tTransport type : %s\n", user_param->num_of_qps, transport_str(user_param->transport_type)); printf(" Connection type : %s\t\tUsing SRQ : %s\n", connStr[user_param->connection_type], user_param->use_srq ? "ON" : "OFF"); #ifdef HAVE_RO - printf(" PCIe relax order: %s\n", user_param->disable_pcir ? "OFF" : "ON"); + #ifdef HAVE_TD_API + printf(" PCIe relax order: %s\t\tLock-free : %s\n", user_param->disable_pcir ? "OFF" : "ON", user_param->no_lock ? "ON" : "OFF"); + #else + printf(" PCIe relax order: %s\t\tLock-free : %s\n", user_param->disable_pcir ? "OFF" : "ON", "Unsupported"); + #endif //HAVE_TD_API if ((check_pcie_relaxed_ordering_compliant() == false) && (user_param->disable_pcir == 0)) { printf(" WARNING: CPU is not PCIe relaxed ordering compliant.\n"); printf(" WARNING: You should disable PCIe RO with `--disable_pcie_relaxed` for both server and client.\n"); } #else - printf(" PCIe relax order: %s\n", "Unsupported"); + #ifdef HAVE_TD_API + printf(" PCIe relax order: %s\t\tLock-free : %s\n", "Unsupported", user_param->no_lock ? "ON" : "OFF"); + #else + printf(" PCIe relax order: %s\t\tLock-free : %s\n", "Unsupported", "Unsupported"); + #endif //HAVE_TD_API #endif + printf(" ibv_wr* API : %s\n", user_param->use_old_post_send ? "OFF" : "ON"); if (user_param->machine == CLIENT || user_param->duplex) { printf(" TX depth : %d\n",user_param->tx_depth); diff --git a/src/perftest_parameters.h b/src/perftest_parameters.h index d26253d..e809c81 100755 --- a/src/perftest_parameters.h +++ b/src/perftest_parameters.h @@ -523,6 +523,7 @@ struct perftest_parameters { int recv_post_list; int duration; int use_srq; + int no_lock; int congest_type; int use_xrc; int use_rss; diff --git a/src/perftest_resources.c b/src/perftest_resources.c index be3890c..40b7ddf 100755 --- a/src/perftest_resources.c +++ b/src/perftest_resources.c @@ -1317,6 +1317,20 @@ int destroy_ctx(struct pingpong_context *ctx, } #endif + #ifdef HAVE_TD_API + if (user_param->no_lock) { + if (ibv_dealloc_pd(ctx->pad)) { + fprintf(stderr, "Failed to deallocate PAD - %s\n", strerror(errno)); + test_result = 1; + } + + if (ibv_dealloc_td(ctx->td)) { + fprintf(stderr, "Failed to deallocate TD - %s\n", strerror(errno)); + test_result = 1; + } + } + #endif + if (ibv_dealloc_pd(ctx->pd)) { fprintf(stderr, "Failed to deallocate PD - %s\n", strerror(errno)); test_result = 1; @@ -1517,6 +1531,47 @@ int create_reg_cqs(struct pingpong_context *ctx, struct perftest_parameters *user_param, int tx_buffer_depth, int need_recv_cq) { +#ifdef HAVE_CQ_EX + struct ibv_cq_init_attr_ex send_cq_attr = { + .cqe = tx_buffer_depth * user_param->num_of_qps, + .cq_context = NULL, + .channel = ctx->send_channel, + .comp_vector = user_param->eq_num, + }; + + #ifdef HAVE_TD_API + if (user_param->no_lock) { + send_cq_attr.parent_domain = ctx->pad; + send_cq_attr.comp_mask = IBV_CQ_INIT_ATTR_MASK_PD; + } + #endif + ctx->send_cq = ibv_cq_ex_to_cq(ibv_create_cq_ex(ctx->context, &send_cq_attr)); + if (!ctx->send_cq) { + fprintf(stderr, "Couldn't create CQ\n"); + return FAILURE; + } + + if (need_recv_cq) { + struct ibv_cq_init_attr_ex recv_cq_attr = { + .cqe = user_param->rx_depth * user_param->num_of_qps, + .cq_context = NULL, + .channel = ctx->recv_channel, + .comp_vector = user_param->eq_num, + }; + #ifdef HAVE_TD_API + if (user_param->no_lock) { + recv_cq_attr.parent_domain = ctx->pad; + recv_cq_attr.comp_mask = IBV_CQ_INIT_ATTR_MASK_PD; + } + #endif + ctx->recv_cq = ibv_cq_ex_to_cq(ibv_create_cq_ex(ctx->context, &recv_cq_attr)); + if (!ctx->recv_cq) { + fprintf(stderr, "Couldn't create a receiver CQ\n"); + return FAILURE; + } + } + return SUCCESS; +#else ctx->send_cq = ibv_create_cq(ctx->context,tx_buffer_depth * user_param->num_of_qps, NULL, ctx->send_channel, user_param->eq_num); if (!ctx->send_cq) { @@ -1534,6 +1589,7 @@ int create_reg_cqs(struct pingpong_context *ctx, } return SUCCESS; +#endif } /****************************************************************************** @@ -1941,6 +1997,30 @@ int ctx_init(struct pingpong_context *ctx, struct perftest_parameters *user_para goto comp_channel; } + #ifdef HAVE_TD_API + /* Allocating the Thread domain, Parent domain. */ + if (user_param->no_lock) { + struct ibv_td_init_attr td_attr = {0}; + ctx->td = ibv_alloc_td(ctx->context, &td_attr); + if (!ctx->td) { + fprintf(stderr, "Couldn't allocate TD\n"); + goto pd; + } + + struct ibv_parent_domain_init_attr pad_attr = { + .pd = ctx->pd, + .td = ctx->td, + .comp_mask = 0, + }; + + ctx->pad = ibv_alloc_parent_domain(ctx->context, &pad_attr); + if (!ctx->pad) { + fprintf(stderr, "Couldn't allocate PAD\n"); + goto td; + } + } + #endif + #ifdef HAVE_AES_XTS if(user_param->aes_xts){ struct mlx5dv_dek_init_attr dek_attr = {}; @@ -2126,6 +2206,16 @@ dek: mlx5dv_dek_destroy(ctx->dek[i]); #endif +#ifdef HAVE_TD_API + if (user_param->no_lock) + ibv_dealloc_pd(ctx->pad); + +td: + if (user_param->no_lock) + ibv_dealloc_td(ctx->td); +pd: +#endif + ibv_dealloc_pd(ctx->pd); comp_channel: diff --git a/src/perftest_resources.h b/src/perftest_resources.h index 565deda..6d95d75 100755 --- a/src/perftest_resources.h +++ b/src/perftest_resources.h @@ -178,6 +178,10 @@ struct pingpong_context { struct ibv_comp_channel *recv_channel; struct ibv_comp_channel *send_channel; struct ibv_pd *pd; + #ifdef HAVE_TD_API + struct ibv_td *td; + struct ibv_pd *pad; + #endif struct ibv_mr **mr; struct ibv_mr *null_mr; struct ibv_cq *send_cq; -- 2.33.0

1 0

优秀贡献者评选
by openEuler conference 10 Nov '23

10 Nov '23

您好！ sig-high-performance-network SIG 邀请您参加 2023-11-17 14:00 召开的Zoom会议(自动录制) 会议主题：优秀贡献者评选会议内容：优秀贡献者评选会议链接：https://us06web.zoom.us/j/86912977154?pwd=bPrifUYIahRJ7ELIV1XCBNF5SbGkBy.1 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-network-meetings 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the Zoom conference(auto recording) will be held at 2023-11-17 14:00, The subject of the conference is 优秀贡献者评选, Summary: 优秀贡献者评选 You can join the meeting at https://us06web.zoom.us/j/86912977154?pwd=bPrifUYIahRJ7ELIV1XCBNF5SbGkBy.1. Add topics at https://etherpad.openeuler.org/p/sig-high-performance-network-meetings. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

高性能网络sig例会
by openEuler conference 12 Jun '23

12 Jun '23

您好！ sig-high-performance-network SIG 邀请您参加 2023-06-15 14:00 召开的Zoom会议会议主题：高性能网络sig例会会议链接：https://us06web.zoom.us/j/89596890142?pwd=YW05N0lyanl5bGhNd3JRdkU1V3YwQT09 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-network-meetings 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the Zoom conference will be held at 2023-06-15 14:00, The subject of the conference is 高性能网络sig例会, You can join the meeting at https://us06web.zoom.us/j/89596890142?pwd=YW05N0lyanl5bGhNd3JRdkU1V3YwQT09. Add topics at https://etherpad.openeuler.org/p/sig-high-performance-network-meetings. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

高性能网络SIG会议
by openEuler conference 12 Dec '22

12 Dec '22

您好！ sig-high-performance-network SIG 邀请您参加 2022-12-15 14:15 召开的Zoom会议(自动录制) 会议主题：高性能网络SIG会议会议内容： 1，服务网格加速技术交流 2，基于FPGA加速平台的分布式人工智能RDMA网络特性研究。评审设计及测试结果会议链接：https://us06web.zoom.us/j/83803700474?pwd=bTkvOEo0RmtsN0tOTCtHUzlDSTVodz09 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-network-meetings 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the Zoom conference(auto recording) will be held at 2022-12-15 14:15, The subject of the conference is 高性能网络SIG会议, Summary: 1，服务网格加速技术交流 2，基于FPGA加速平台的分布式人工智能RDMA网络特性研究。评审设计及测试结果 You can join the meeting at https://us06web.zoom.us/j/83803700474?pwd=bTkvOEo0RmtsN0tOTCtHUzlDSTVodz09. Add topics at https://etherpad.openeuler.org/p/sig-high-performance-network-meetings. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

[PATCH] update dpdk.spec due to backporting patches
by Huisong Li 24 Oct '22

24 Oct '22

Update dpdk.spec due to backporting PMD and lib patches. Signed-off-by: Huisong Li <lihuisong(a)huawei.com> --- dpdk.spec | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 76 insertions(+), 1 deletion(-) diff --git a/dpdk.spec b/dpdk.spec index d5522d1..971a988 100644 --- a/dpdk.spec +++ b/dpdk.spec @@ -1,6 +1,6 @@ Name: dpdk Version: 21.11 -Release: 18 +Release: 19 Packager: packaging(a)6wind.com URL: http://dpdk.org %global source_version 21.11 @@ -137,6 +137,72 @@ Patch6003: backport-0001-CVE-2022-2132.patch Patch6004: backport-0002-CVE-2022-2132.patch Patch6005: backport-CVE-2022-28199.patch +Patch9125: 0125-net-hns3-fix-link-status-capability-query-from-VF.patch +Patch9126: 0126-net-hns3-support-backplane-media-type.patch +Patch9127: 0127-net-hns3-cancel-heartbeat-alarm-when-VF-reset.patch +Patch9128: 0128-net-hns3-fix-PTP-interrupt-logging.patch +Patch9129: 0129-net-hns3-fix-statistics-locking.patch +Patch9130: 0130-net-hns3-fix-descriptors-check-with-SVE.patch +Patch9131: 0131-net-hns3-clean-some-functions.patch +Patch9132: 0132-net-hns3-delete-unused-code.patch +Patch9133: 0133-examples-dma-support-dequeue-when-no-packet-received.patch +Patch9134: 0134-net-hns3-add-dump-of-VF-VLAN-filter-modify-capabilit.patch +Patch9135: 0135-net-hns3-fix-Rx-with-PTP.patch +Patch9136: 0136-net-hns3-fix-crash-in-SVE-Tx.patch +Patch9137: 0137-net-hns3-fix-next-to-use-overflow-in-SVE-Tx.patch +Patch9138: 0138-net-hns3-fix-next-to-use-overflow-in-simple-Tx.patch +Patch9139: 0139-net-hns3-optimize-SVE-Tx-performance.patch +Patch9140: 0140-net-hns3-fix-crash-when-secondary-process-access-FW.patch +Patch9141: 0141-net-hns3-delete-unused-markup.patch +Patch9142: 0142-net-hns3-fix-clearing-hardware-MAC-statistics.patch +Patch9143: 0143-net-hns3-revert-Tx-performance-optimization.patch +Patch9144: 0144-net-hns3-fix-RSS-rule-restore.patch +Patch9145: 0145-net-hns3-fix-RSS-filter-restore.patch +Patch9146: 0146-net-hns3-fix-lock-protection-of-RSS-flow-rule.patch +Patch9147: 0147-net-hns3-fix-RSS-flow-rule-restore.patch +Patch9148: 0148-net-hns3-move-flow-direction-rule-recovery.patch +Patch9149: 0149-net-hns3-fix-restore-filter-function-input.patch +Patch9150: 0150-net-hns3-fix-build-with-gcov.patch +Patch9151: 0151-net-hns3-fix-packet-type-for-GENEVE.patch +Patch9152: 0152-net-hns3-remove-magic-numbers-for-MAC-address.patch +Patch9153: 0153-net-hns3-fix-code-check-warnings.patch +Patch9154: 0154-net-hns3-fix-header-files-includes.patch +Patch9155: 0155-net-hns3-remove-unused-structures.patch +Patch9156: 0156-net-hns3-rename-header-guards.patch +Patch9157: 0157-net-hns3-fix-IPv4-and-IPv6-RSS.patch +Patch9158: 0158-net-hns3-fix-types-in-IPv6-SCTP-fields.patch +Patch9159: 0159-net-hns3-fix-IPv4-RSS.patch +Patch9160: 0160-net-hns3-add-check-for-L3-and-L4-type.patch +Patch9161: 0161-net-hns3-revert-fix-mailbox-communication-with-HW.patch +Patch9162: 0162-net-hns3-fix-VF-mailbox-message-handling.patch +Patch9163: 0163-net-hns3-fix-minimum-Tx-frame-length.patch +Patch9164: 0164-ethdev-introduce-Rx-Tx-descriptor-dump-API.patch +Patch9165: 0165-net-hns3-support-Rx-Tx-descriptor-dump.patch +Patch9166: 0166-remove-unnecessary-null-checks.patch +Patch9167: 0167-ethdev-introduce-generic-dummy-packet-burst-function.patch +Patch9168: 0168-fix-spelling-in-comments-and-strings.patch +Patch9169: 0169-net-hns3-add-VLAN-filter-query-in-dump-file.patch +Patch9170: 0170-net-bonding-fix-array-overflow-in-Rx-burst.patch +Patch9171: 0171-net-bonding-fix-double-slave-link-status-query.patch +Patch9172: 0172-app-testpmd-fix-supported-RSS-offload-display.patch +Patch9173: 0173-app-testpmd-unify-name-of-L2-payload-offload.patch +Patch9174: 0174-app-testpmd-refactor-config-all-RSS-command.patch +Patch9175: 0175-app-testpmd-unify-RSS-types-display.patch +Patch9176: 0176-app-testpmd-compact-RSS-types-output.patch +Patch9177: 0177-app-testpmd-reorder-RSS-type-table.patch +Patch9178: 0178-app-testpmd-fix-RSS-types-display.patch +Patch9179: 0179-ethdev-support-telemetry-private-dump.patch +Patch9180: 0180-dmadev-add-telemetry.patch +Patch9181: 0181-dmadev-support-telemetry-dump-dmadev.patch +Patch9182: 0182-telemetry-add-missing-C-guards.patch +Patch9183: 0183-telemetry-add-missing-C-guards.patch +Patch9184: 0184-telemetry-fix-escaping-of-invalid-json-characters.patch +Patch9185: 0185-telemetry-add-escaping-of-strings-in-arrays.patch +Patch9186: 0186-telemetry-add-escaping-of-strings-in-dicts.patch +Patch9187: 0187-telemetry-limit-command-characters.patch +Patch9188: 0188-telemetry-eliminate-duplicate-code-for-json-output.patch +Patch9189: 0189-telemetry-make-help-command-more-helpful.patch + Summary: Data Plane Development Kit core Group: System Environment/Libraries License: BSD and LGPLv2 and GPLv2 @@ -264,6 +330,15 @@ strip -g $RPM_BUILD_ROOT/lib/modules/%{kern_devel_ver}/extra/dpdk/igb_uio.ko /usr/sbin/depmod %changelog +* Thu Oct 21 2022 Huisong Li <lihuisong(a)huawei.com> - 21.11-19 +- add some bugfixes for hns3 +- revert Tx performance optimization for hns3 +- refactor some RSS commands for testpmd +- add Rx/Tx descriptor dump feature for hns3 +- add ethdev telemetry private dump +- add dmadev telemetry +- sync telemetry lib + * Thu Oct 6 2022 wuchangsheng <wuchangsheng2(a)huawei.com> - 21.11-18 - reinit support return ok -- 2.30.0

3 67

[PATCH] update dpdk.spec due to backporting patches
by Huisong Li 21 Oct '22

21 Oct '22

Update dpdk.spec due to backporting PMD and lib patches. Signed-off-by: Huisong Li <lihuisong(a)huawei.com> --- dpdk.spec | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 76 insertions(+), 1 deletion(-) diff --git a/dpdk.spec b/dpdk.spec index d5522d1..971a988 100644 --- a/dpdk.spec +++ b/dpdk.spec @@ -1,6 +1,6 @@ Name: dpdk Version: 21.11 -Release: 18 +Release: 19 Packager: packaging(a)6wind.com URL: http://dpdk.org %global source_version 21.11 @@ -137,6 +137,72 @@ Patch6003: backport-0001-CVE-2022-2132.patch Patch6004: backport-0002-CVE-2022-2132.patch Patch6005: backport-CVE-2022-28199.patch +Patch9125: 0125-net-hns3-fix-link-status-capability-query-from-VF.patch +Patch9126: 0126-net-hns3-support-backplane-media-type.patch +Patch9127: 0127-net-hns3-cancel-heartbeat-alarm-when-VF-reset.patch +Patch9128: 0128-net-hns3-fix-PTP-interrupt-logging.patch +Patch9129: 0129-net-hns3-fix-statistics-locking.patch +Patch9130: 0130-net-hns3-fix-descriptors-check-with-SVE.patch +Patch9131: 0131-net-hns3-clean-some-functions.patch +Patch9132: 0132-net-hns3-delete-unused-code.patch +Patch9133: 0133-examples-dma-support-dequeue-when-no-packet-received.patch +Patch9134: 0134-net-hns3-add-dump-of-VF-VLAN-filter-modify-capabilit.patch +Patch9135: 0135-net-hns3-fix-Rx-with-PTP.patch +Patch9136: 0136-net-hns3-fix-crash-in-SVE-Tx.patch +Patch9137: 0137-net-hns3-fix-next-to-use-overflow-in-SVE-Tx.patch +Patch9138: 0138-net-hns3-fix-next-to-use-overflow-in-simple-Tx.patch +Patch9139: 0139-net-hns3-optimize-SVE-Tx-performance.patch +Patch9140: 0140-net-hns3-fix-crash-when-secondary-process-access-FW.patch +Patch9141: 0141-net-hns3-delete-unused-markup.patch +Patch9142: 0142-net-hns3-fix-clearing-hardware-MAC-statistics.patch +Patch9143: 0143-net-hns3-revert-Tx-performance-optimization.patch +Patch9144: 0144-net-hns3-fix-RSS-rule-restore.patch +Patch9145: 0145-net-hns3-fix-RSS-filter-restore.patch +Patch9146: 0146-net-hns3-fix-lock-protection-of-RSS-flow-rule.patch +Patch9147: 0147-net-hns3-fix-RSS-flow-rule-restore.patch +Patch9148: 0148-net-hns3-move-flow-direction-rule-recovery.patch +Patch9149: 0149-net-hns3-fix-restore-filter-function-input.patch +Patch9150: 0150-net-hns3-fix-build-with-gcov.patch +Patch9151: 0151-net-hns3-fix-packet-type-for-GENEVE.patch +Patch9152: 0152-net-hns3-remove-magic-numbers-for-MAC-address.patch +Patch9153: 0153-net-hns3-fix-code-check-warnings.patch +Patch9154: 0154-net-hns3-fix-header-files-includes.patch +Patch9155: 0155-net-hns3-remove-unused-structures.patch +Patch9156: 0156-net-hns3-rename-header-guards.patch +Patch9157: 0157-net-hns3-fix-IPv4-and-IPv6-RSS.patch +Patch9158: 0158-net-hns3-fix-types-in-IPv6-SCTP-fields.patch +Patch9159: 0159-net-hns3-fix-IPv4-RSS.patch +Patch9160: 0160-net-hns3-add-check-for-L3-and-L4-type.patch +Patch9161: 0161-net-hns3-revert-fix-mailbox-communication-with-HW.patch +Patch9162: 0162-net-hns3-fix-VF-mailbox-message-handling.patch +Patch9163: 0163-net-hns3-fix-minimum-Tx-frame-length.patch +Patch9164: 0164-ethdev-introduce-Rx-Tx-descriptor-dump-API.patch +Patch9165: 0165-net-hns3-support-Rx-Tx-descriptor-dump.patch +Patch9166: 0166-remove-unnecessary-null-checks.patch +Patch9167: 0167-ethdev-introduce-generic-dummy-packet-burst-function.patch +Patch9168: 0168-fix-spelling-in-comments-and-strings.patch +Patch9169: 0169-net-hns3-add-VLAN-filter-query-in-dump-file.patch +Patch9170: 0170-net-bonding-fix-array-overflow-in-Rx-burst.patch +Patch9171: 0171-net-bonding-fix-double-slave-link-status-query.patch +Patch9172: 0172-app-testpmd-fix-supported-RSS-offload-display.patch +Patch9173: 0173-app-testpmd-unify-name-of-L2-payload-offload.patch +Patch9174: 0174-app-testpmd-refactor-config-all-RSS-command.patch +Patch9175: 0175-app-testpmd-unify-RSS-types-display.patch +Patch9176: 0176-app-testpmd-compact-RSS-types-output.patch +Patch9177: 0177-app-testpmd-reorder-RSS-type-table.patch +Patch9178: 0178-app-testpmd-fix-RSS-types-display.patch +Patch9179: 0179-ethdev-support-telemetry-private-dump.patch +Patch9180: 0180-dmadev-add-telemetry.patch +Patch9181: 0181-dmadev-support-telemetry-dump-dmadev.patch +Patch9182: 0182-telemetry-add-missing-C-guards.patch +Patch9183: 0183-telemetry-add-missing-C-guards.patch +Patch9184: 0184-telemetry-fix-escaping-of-invalid-json-characters.patch +Patch9185: 0185-telemetry-add-escaping-of-strings-in-arrays.patch +Patch9186: 0186-telemetry-add-escaping-of-strings-in-dicts.patch +Patch9187: 0187-telemetry-limit-command-characters.patch +Patch9188: 0188-telemetry-eliminate-duplicate-code-for-json-output.patch +Patch9189: 0189-telemetry-make-help-command-more-helpful.patch + Summary: Data Plane Development Kit core Group: System Environment/Libraries License: BSD and LGPLv2 and GPLv2 @@ -264,6 +330,15 @@ strip -g $RPM_BUILD_ROOT/lib/modules/%{kern_devel_ver}/extra/dpdk/igb_uio.ko /usr/sbin/depmod %changelog +* Thu Oct 21 2022 Huisong Li <lihuisong(a)huawei.com> - 21.11-19 +- add some bugfixes for hns3 +- revert Tx performance optimization for hns3 +- refactor some RSS commands for testpmd +- add Rx/Tx descriptor dump feature for hns3 +- add ethdev telemetry private dump +- add dmadev telemetry +- sync telemetry lib + * Thu Oct 6 2022 wuchangsheng <wuchangsheng2(a)huawei.com> - 21.11-18 - reinit support return ok -- 2.30.0

1 65

[PATCH] update dpdk.spec due to backporting patches
by Huisong Li 21 Oct '22

21 Oct '22

Update dpdk.spec due to backporting PMD and lib patches. Signed-off-by: Huisong Li <lihuisong(a)huawei.com> --- dpdk.spec | 77 ++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 76 insertions(+), 1 deletion(-) diff --git a/dpdk.spec b/dpdk.spec index d5522d1..971a988 100644 --- a/dpdk.spec +++ b/dpdk.spec @@ -1,6 +1,6 @@ Name: dpdk Version: 21.11 -Release: 18 +Release: 19 Packager: packaging(a)6wind.com URL: http://dpdk.org %global source_version 21.11 @@ -137,6 +137,72 @@ Patch6003: backport-0001-CVE-2022-2132.patch Patch6004: backport-0002-CVE-2022-2132.patch Patch6005: backport-CVE-2022-28199.patch +Patch9125: 0125-net-hns3-fix-link-status-capability-query-from-VF.patch +Patch9126: 0126-net-hns3-support-backplane-media-type.patch +Patch9127: 0127-net-hns3-cancel-heartbeat-alarm-when-VF-reset.patch +Patch9128: 0128-net-hns3-fix-PTP-interrupt-logging.patch +Patch9129: 0129-net-hns3-fix-statistics-locking.patch +Patch9130: 0130-net-hns3-fix-descriptors-check-with-SVE.patch +Patch9131: 0131-net-hns3-clean-some-functions.patch +Patch9132: 0132-net-hns3-delete-unused-code.patch +Patch9133: 0133-examples-dma-support-dequeue-when-no-packet-received.patch +Patch9134: 0134-net-hns3-add-dump-of-VF-VLAN-filter-modify-capabilit.patch +Patch9135: 0135-net-hns3-fix-Rx-with-PTP.patch +Patch9136: 0136-net-hns3-fix-crash-in-SVE-Tx.patch +Patch9137: 0137-net-hns3-fix-next-to-use-overflow-in-SVE-Tx.patch +Patch9138: 0138-net-hns3-fix-next-to-use-overflow-in-simple-Tx.patch +Patch9139: 0139-net-hns3-optimize-SVE-Tx-performance.patch +Patch9140: 0140-net-hns3-fix-crash-when-secondary-process-access-FW.patch +Patch9141: 0141-net-hns3-delete-unused-markup.patch +Patch9142: 0142-net-hns3-fix-clearing-hardware-MAC-statistics.patch +Patch9143: 0143-net-hns3-revert-Tx-performance-optimization.patch +Patch9144: 0144-net-hns3-fix-RSS-rule-restore.patch +Patch9145: 0145-net-hns3-fix-RSS-filter-restore.patch +Patch9146: 0146-net-hns3-fix-lock-protection-of-RSS-flow-rule.patch +Patch9147: 0147-net-hns3-fix-RSS-flow-rule-restore.patch +Patch9148: 0148-net-hns3-move-flow-direction-rule-recovery.patch +Patch9149: 0149-net-hns3-fix-restore-filter-function-input.patch +Patch9150: 0150-net-hns3-fix-build-with-gcov.patch +Patch9151: 0151-net-hns3-fix-packet-type-for-GENEVE.patch +Patch9152: 0152-net-hns3-remove-magic-numbers-for-MAC-address.patch +Patch9153: 0153-net-hns3-fix-code-check-warnings.patch +Patch9154: 0154-net-hns3-fix-header-files-includes.patch +Patch9155: 0155-net-hns3-remove-unused-structures.patch +Patch9156: 0156-net-hns3-rename-header-guards.patch +Patch9157: 0157-net-hns3-fix-IPv4-and-IPv6-RSS.patch +Patch9158: 0158-net-hns3-fix-types-in-IPv6-SCTP-fields.patch +Patch9159: 0159-net-hns3-fix-IPv4-RSS.patch +Patch9160: 0160-net-hns3-add-check-for-L3-and-L4-type.patch +Patch9161: 0161-net-hns3-revert-fix-mailbox-communication-with-HW.patch +Patch9162: 0162-net-hns3-fix-VF-mailbox-message-handling.patch +Patch9163: 0163-net-hns3-fix-minimum-Tx-frame-length.patch +Patch9164: 0164-ethdev-introduce-Rx-Tx-descriptor-dump-API.patch +Patch9165: 0165-net-hns3-support-Rx-Tx-descriptor-dump.patch +Patch9166: 0166-remove-unnecessary-null-checks.patch +Patch9167: 0167-ethdev-introduce-generic-dummy-packet-burst-function.patch +Patch9168: 0168-fix-spelling-in-comments-and-strings.patch +Patch9169: 0169-net-hns3-add-VLAN-filter-query-in-dump-file.patch +Patch9170: 0170-net-bonding-fix-array-overflow-in-Rx-burst.patch +Patch9171: 0171-net-bonding-fix-double-slave-link-status-query.patch +Patch9172: 0172-app-testpmd-fix-supported-RSS-offload-display.patch +Patch9173: 0173-app-testpmd-unify-name-of-L2-payload-offload.patch +Patch9174: 0174-app-testpmd-refactor-config-all-RSS-command.patch +Patch9175: 0175-app-testpmd-unify-RSS-types-display.patch +Patch9176: 0176-app-testpmd-compact-RSS-types-output.patch +Patch9177: 0177-app-testpmd-reorder-RSS-type-table.patch +Patch9178: 0178-app-testpmd-fix-RSS-types-display.patch +Patch9179: 0179-ethdev-support-telemetry-private-dump.patch +Patch9180: 0180-dmadev-add-telemetry.patch +Patch9181: 0181-dmadev-support-telemetry-dump-dmadev.patch +Patch9182: 0182-telemetry-add-missing-C-guards.patch +Patch9183: 0183-telemetry-add-missing-C-guards.patch +Patch9184: 0184-telemetry-fix-escaping-of-invalid-json-characters.patch +Patch9185: 0185-telemetry-add-escaping-of-strings-in-arrays.patch +Patch9186: 0186-telemetry-add-escaping-of-strings-in-dicts.patch +Patch9187: 0187-telemetry-limit-command-characters.patch +Patch9188: 0188-telemetry-eliminate-duplicate-code-for-json-output.patch +Patch9189: 0189-telemetry-make-help-command-more-helpful.patch + Summary: Data Plane Development Kit core Group: System Environment/Libraries License: BSD and LGPLv2 and GPLv2 @@ -264,6 +330,15 @@ strip -g $RPM_BUILD_ROOT/lib/modules/%{kern_devel_ver}/extra/dpdk/igb_uio.ko /usr/sbin/depmod %changelog +* Thu Oct 21 2022 Huisong Li <lihuisong(a)huawei.com> - 21.11-19 +- add some bugfixes for hns3 +- revert Tx performance optimization for hns3 +- refactor some RSS commands for testpmd +- add Rx/Tx descriptor dump feature for hns3 +- add ethdev telemetry private dump +- add dmadev telemetry +- sync telemetry lib + * Thu Oct 6 2022 wuchangsheng <wuchangsheng2(a)huawei.com> - 21.11-18 - reinit support return ok -- 2.30.0

1 65

2022年4月14日SIG开发者大会议题材料及视频（补充到邮件列表） ---- K8s
by wuchangsheng (C) 01 Sep '22

01 Sep '22

4. K8s大规模集群下负载均衡性能问题及优化方案（谢颂杨）随着容器业务的快速增长，容器的部署密度越来越大，大规模集群越来越常见。大规模集群场景下，k8s原生服务负载均衡机制成为了性能瓶颈，针对这个问题结合业界常用的优化方案进行探讨。大规模集群性能问题介绍业界常见优化方案 SPE方案介绍及效果展示开发者大会视频链接：https://www.bilibili.com/video/BV1o44y1V7ao?spm_id_from=333.337.search… 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-networking-22.09…

1 0

2022年4月14日SIG开发者大会议题材料及视频（补充到邮件列表） ---- RDMA
by wuchangsheng (C) 01 Sep '22

01 Sep '22

3. 高性能网络之RDMA技术演进(李扬扬): RDMA(Remote Direct Memory Access)技术追求极致性能，与传统 TCP/IP 实现相比，节省了协议处理和数据拷贝所需的 CPU 资源，同时也提高了网络吞吐量、降低了网络通信时延。越来越多厂家加入RDMA技术的研究，推出了自己的硬件产品。这些产品在HPC场景和云场景下已广泛应用，但在大数据、存储等领域进展缓慢。梳理RDMA技术推广遇到的困难，并讨论技术演进的策略。 RDMA生态各厂家技术路线介绍 RDMA生态发展趋势讨论：异常处理，节省内存，CPU卸载，IO提速、资源创建提速等开发者大会视频链接：https://www.bilibili.com/video/BV1o44y1V7ao?spm_id_from=333.337.search… 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-networking-22.09…

1 0

2022年4月14日SIG开发者大会议题材料及视频（补充到邮件列表） ---- tcpm
by wuchangsheng (C) 01 Sep '22

01 Sep '22

2.CDN场景网络带宽问题及解决方案――TCPM智能反馈负载均衡(曹汪宝): TCPM作为CDN加速场景的一项杀手级技术，在视频直播中应用中效果尤为显著，与传统CDN场景相比减少了CDN板间流量，减少服务器40%+。 CDN场景网络带宽问题介绍 TCPM技术方案介绍开发者大会视频链接：https://www.bilibili.com/video/BV1o44y1V7ao?spm_id_from=333.337.search… 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-networking-22.09…

1 0

2022年4月14日SIG开发者大会议题材料及视频（补充到邮件列表） ---- Gazelle
by wuchangsheng (C) 01 Sep '22

01 Sep '22

1. 数据库加速问题介绍及解决方案――Gazelle用户态协议栈 Gazelle是一款高性能通用用户态协议栈，专注于数据库网络性能加速，如MySQL提升10%+、openGauss提升2.66倍: 数据库场景加速面临的问题 Gazelle技术方案介绍加速效果展示后续规划单独介绍视频：https://www.bilibili.com/video/BV14a411D7ob?spm_id_from=333.337.sear… 开发者大会视频链接：https://www.bilibili.com/video/BV1o44y1V7ao?spm_id_from=333.337.search… 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-networking-22.09…

1 0

【2022-09-01 高性能网络SIG会议纪要】
by wuchangsheng (C) 01 Sep '22

01 Sep '22

本次会议视频会自动上传B站，一般第二天可看到视频。议题一：增加SIG突出贡献者名单 SIG成员分为三类 maintainer commiter 贡献值。由于贡献者人数太多，只列出突出贡献者。本次新增两人 gitee昵称 giteeID 邮箱姓名(可选) yyang yyangoO yyangoo(a)outlook.com<mailto:yyangoo@outlook.com> 杨洋 honggangli honggangli22 honggangli(a)163.com<mailto:honggangli@163.com> 黎红刚议题二：虚拟化场景加速ceph方案介绍介绍材料见附件

1 0

张县婷已经接受你的邀请: 高性能网络SIG会议
by 张县婷 31 Aug '22

31 Aug '22

张县婷已经接受你的邀请: [High-performance-network] 高性能网络SIG会议

1 0

高性能网络SIG会议
by openEuler conference 31 Aug '22

31 Aug '22

您好！ sig-high-performance-network SIG 邀请您参加 2022-09-01 14:15 召开的Zoom会议(自动录制) 会议主题：高性能网络SIG会议会议内容： 1，增加SIG突出贡献者名单 2，虚拟化场景加速ceph方案介绍会议链接：https://us06web.zoom.us/j/85782756673?pwd=SjREMitZcE1icVh3WTBXQ1dJRkdkZz09 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-network-meetings 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the Zoom conference(auto recording) will be held at 2022-09-01 14:15, The subject of the conference is 高性能网络SIG会议, Summary: 1，增加SIG突出贡献者名单 2，虚拟化场景加速ceph方案介绍 You can join the meeting at https://us06web.zoom.us/j/85782756673?pwd=SjREMitZcE1icVh3WTBXQ1dJRkdkZz09. Add topics at https://etherpad.openeuler.org/p/sig-high-performance-network-meetings. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

[Cancel] 高性能网络sig例会
by openEuler conference 31 Aug '22

31 Aug '22

Sorry! The Zoom meeting will be held at 2022-09-01 19:00 scheduled by openEuler sig-high-performance-network SIG has been cancelled.

1 0

高性能网络sig例会
by openEuler conference 23 Aug '22

23 Aug '22

您好！ sig-high-performance-network SIG 邀请您参加 2022-09-01 19:00 召开的Zoom会议(自动录制) 会议主题：高性能网络sig例会会议内容： 1，议题征集中会议链接：https://us06web.zoom.us/j/86989474827?pwd=dTE1SnpTNXZSaTBIalZRMlErNC83dz09 会议纪要：https://etherpad.openeuler.org/p/sig-high-performance-network-meetings 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the Zoom conference(auto recording) will be held at 2022-09-01 19:00, The subject of the conference is 高性能网络sig例会, Summary: 1，议题征集中 You can join the meeting at https://us06web.zoom.us/j/86989474827?pwd=dTE1SnpTNXZSaTBIalZRMlErNC83dz09. Add topics at https://etherpad.openeuler.org/p/sig-high-performance-network-meetings. Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com. More information: https://openeuler.org/en/

1 0

【会议纪要】答复: 【会议通知】高性能网络SIG例会，时间：2022-08-11 19:00-20:30(UTC+08:00)，
by wuchangsheng (C) 13 Aug '22

13 Aug '22

议题一：SIG例会运作讨论 1，每次SIG例会录屏并上传至B站 2，通过邮件列表申报议题，通知会议，讨论问题 3， SIG例会评审建仓，commiter增删。以技术交流为主，分享论文、技术介绍。议题二：基于FPGA加速平台进行分布式人工智能RDMA网络通信研究，GNFC算法设计方案评审当前设计方案为初始版本，暂不考虑交换机队列深度因素。方案评审通过在openEuler建仓提交代码及方案文档团队申请1~2名commiter 设计方案见附件议题三：混合部署场景基ED模型网络出口QoS控制――POD带宽管理代码仓库：https://gitee.com/openeuler/oncn-bwm 分享材料见附件 PS：本次SIG例会，由于预定会议方式错误，导致会议视频无法上传B站。后续SIG例会，改为openEuler小程序预定会议，会议自动录屏第二天自动上传B站发件人: wuchangsheng (C) via High-performance-network [mailto:high-performance-network@openeuler.org] 发送时间: 2022年8月8日 12:00 收件人: high-performance-network(a)openeuler.org 主题: [High-performance-network] 答复: 【会议通知】高性能网络SIG例会，时间：2022-08-11 19:00-20:30(UTC+08:00)，当前议题如下，回复邮件申报议题会议议题 Agenda 编号 No. 议题名称 Topic 议题类型 Category 时长 Duration 起止时间 Time 提案人 Proposer 汇报人 Reporter 纪要人 Recorder 议题参与人 Members 1 SIG例会运作讨论汇报类 10min 19:00-19:10 吴昌盛 2 基于FPGA加速平台进行分布式人工智能RDMA网络通信研究，GNFC算法设计方案评审汇报类 30min 19:10-19:40 张乙然 3 混合部署场景基于EDT模型网络出口QoS控制――POD带宽管理汇报类 30min 19:40-20:10 牛芊芊发件人: Meeting Book via High-performance-network [mailto:high-performance-network@openeuler.org] 发送时间: 2022年8月8日 11:52 主题: [High-performance-network] 【会议通知】高性能网络SIG例会，时间：2022-08-11 19:00-20:30(UTC+08:00)，会议主题 Subject 高性能网络SIG例会会议时间 Time 2022-08-11 19:00-20:30(UTC+08:00)Beijing Welink视频会议 Welink Video Meeting 加入会议(External)<https://meeting.huaweicloud.com:36443/#/j/98674831/7e6f67d8c84bb2983f71b4cb…> 会议ID Meeting ID 98674831 会议密码 Meeting Passcode 123456 召集人 Convener 吴昌盛提示 Tips 请点击会议链接加入会议,首次使用请在入会界面根据提示下载并安装客户端后输入ID入会。 Click the meeting link to join the meeting. For the first time, download and install the client as prompted and enter the ID to join the meeting

1 0

openEuler-高性能网络SIG例会材料分享——POD带宽管理
by wo_cow 11 Aug '22

11 Aug '22

《混合部署场景基于EDT模型网络出口QoS控制——POD带宽管理》PPT见附件代码仓库：https://gitee.com/openeuler/oncn-bwm

1 0

基于FPGA加速平台的分布式人工智能RDMA网络通信项目GNFC算法
by wsdsfcd 11 Aug '22

11 Aug '22

基于FPGA加速平台的分布式人工智能RDMA网络通信项目GNFC算法

1 0

【会议通知】高性能网络SIG例会，时间：2022-08-11 19:00-20:30(UTC+08:00)，
by Meeting Book 08 Aug '22

08 Aug '22

会议主题 Subject 高性能网络SIG例会会议时间 Time 2022-08-11 19:00-20:30(UTC+08:00)Beijing Welink视频会议 Welink Video Meeting 加入会议(External)<https://meeting.huaweicloud.com:36443/#/j/98674831/7e6f67d8c84bb2983f71b4cb…> 会议ID Meeting ID 98674831 会议密码 Meeting Passcode 123456 召集人 Convener 吴昌盛提示 Tips 请点击会议链接加入会议,首次使用请在入会界面根据提示下载并安装客户端后输入ID入会。 Click the meeting link to join the meeting. For the first time, download and install the client as prompted and enter the ID to join the meeting

2 1

openEuler 22.09 Alpha版本release公告
by chenyaqiang 25 Jul '22

25 Jul '22

Dear all， openEuler 22.09创新版本Alpha版本在经过社区各SIG组协作开发，CI/CD SIG规模构建，及QA SIG Alpha版本质量评估，满足alpha版本发布质量标准，现正式发布该alpha版本，社区各SIG组及所有爱好者均可以下载并试用alpha ，Alpha 版本包含 openEuler 22.09 版本的几乎全量组件（少量持续编译/构建失败包清单详见邮件正文编译构建章节），版本测试能力/策略由 openEuler QA SIG团队指导，社区各个SIG组自主开展组件自验证，社区一起协作支撑openEuler 22.09创新版本issue发现和定位修复，您发现和定位修复每一个issue不仅可以解决您使用openEuler创新版本的问题点，更可以支撑社区一起持续优化提升百万级openEuler用户的体验！ Alpha版本作为beta版本的前置自验证版本，经过社区联合协作自验证和issue修复后，下一个版本里程碑点（预计在2022/08/01）将会提供 Beta 版本。 openEuler 22.09版本release plan公示链接： https://gitee.com/openeuler/release-management/blob/master/openEuler-22.09/… openEuler 22.09 Alpha版本下载链接： http://121.36.84.172/dailybuild/openEuler-22.09/openeuler-2022-07-25-10-43-… openEuler 22.09 Alpha版本发布质量评估规范公示链接： https://gitee.com/openeuler/QA/blob/master/Test_Checklist/%E7%A4%BE%E5%8C%B… openEuler 22.09 Alpha版本自验证进展与质量结果同步方式：建议各sig组及社区用户均可以在QA-sig下以ISSUE方式同步自验证进展和自验证结果，您的自验证结果将是Alpha版本质量评估的充分信息依据；社区QA 版本测试提单规范 https://gitee.com/openeuler/QA/blob/839f952696f271f83c018ccf3218cf493b92d65… 社区QA 测试平台 radiates https://radiatest.openeuler.org<https://radiatest.openeuler.org/> openEuler 22.09 Alpha版本已知待修复单包构建失败问题清单：里程碑地址：https://e.gitee.com/open_euler/milestones/170898/issues/table 里程碑任务ID 任务标题任务状态关联仓库 Sig openEuler-22.09-Dailybuild I5HVUZ ima-evm-utils build problem in openEuler:22.09 待办的 ima-evm-utils Base-service openEuler-22.09-Dailybuild I5HVVF mysql5 build problem in openEuler:22.09 待办的 mysql5 DB openEuler-22.09-Dailybuild I5HZVX folks build problem in openEuler:22.09 待办的 folks GNOME openEuler-22.09-Dailybuild I5HZW3 subunit build problem in openEuler:22.09 待办的 subunit Programming-language openEuler-22.09-Dailybuild I5I1ZZ ceph build problem in openEuler:22.09 待办的 ceph sig-SDS openEuler-22.09-Dailybuild I5I6MO libgit2 build problem in openEuler:22.09 待办的 libgit2 Base-service openEuler-22.09-Dailybuild I5IH5G gpgme build problem in openEuler:22.09 待办的 gpgme Base-service openEuler-22.09-Dailybuild I5IH69 iotop build problem in openEuler:22.09 待办的 iotop Storage openEuler-22.09-Dailybuild I5IH6M libpwquality build problem in openEuler:22.09 待办的 libpwquality sig-security-facility openEuler-22.09-Dailybuild I5IH6T nftables build problem in openEuler:22.09 待办的 nftables Networking openEuler-22.09-Dailybuild I5ILK7 bamf build problem in openEuler:22.09:Epol 待办的 bamf sig-UKUI openEuler-22.09-Dailybuild I5ILK8 vdsm-jsonrpc-java build problem in openEuler:22.09:Epol 待办的 vdsm-jsonrpc-java oVirt openEuler-22.09-Dailybuild I5ILKA python-crypto build problem in openEuler:22.09 待办的 python-crypto Base-service openEuler-22.09-Dailybuild I5ILKE sssd build problem in openEuler:22.09 待办的 sssd Base-service openEuler-22.09-Dailybuild I5IQZF highlight build problem in openEuler:22.09:Epol 待办的 highlight oVirt openEuler 22.09 Alpha版本已知待修复单包安装失败软件包清单：安装校验项架构 jenkins任务地址 ISO二进制范围 x86_64 https://openeulerjenkins.osinfra.cn/job/openEuler-OS-build/job/check_rpm_in… Epol二进制范围 x86_64 https://openeulerjenkins.osinfra.cn/job/openEuler-OS-build/job/check_rpm_in… ISO二进制范围 aarch64 https://openeulerjenkins.osinfra.cn/job/openEuler-OS-build/job/check_rpm_in… Epol二进制范围 aarch64 https://openeulerjenkins.osinfra.cn/job/openEuler-OS-build/job/check_rpm_in… 二进制包名源码包名 Sig python3-jupyter python-jupyter #N/A python3-nni python-nni A-Tune setroubleshoot-plugins setroubleshoot-plugins Base-service backupninja backupninja Application blueman blueman sig-UKUI cinnamon cinnamon sig-cinnamon cinnamon-devel-doc cinnamon sig-cinnamon claws-mail-plugins claws-mail sig-UKUI claws-mail-plugins-bsfilter claws-mail sig-UKUI claws-mail-plugins-bogofilter claws-mail sig-UKUI cockpit-ovirt-dashboard cockpit-ovirt oVirt ovirt-hosted-engine-setup ovirt-hosted-engine-setup oVirt ovirt-host ovirt-host oVirt dde dde sig-DDE dde-control-center dde-control-center sig-DDE startdde startdde sig-DDE dde-daemon dde-daemon sig-DDE dde-session-ui dde-session-ui sig-DDE dde-desktop dde-file-manager sig-DDE dde-launcher dde-launcher sig-DDE dde-file-manager dde-file-manager sig-DDE libdde-file-manager dde-file-manager sig-DDE dde-disk-mount-plugin dde-file-manager sig-DDE dde-file-manager-devel dde-file-manager sig-DDE dde-launcher-devel dde-launcher sig-DDE deepin-compressor deepin-compressor sig-DDE deepin-font-manager deepin-font-manager sig-DDE libdeepin-font-manager deepin-font-manager sig-DDE deepin-screen-recorder deepin-screen-recorder sig-DDE kwin kwin sig-KDE kwin-common kwin sig-KDE kwin-devel kwin sig-KDE kwin-doc kwin sig-KDE kwin-wayland kwin sig-KDE kwin-x11 kwin sig-KDE lastpass-cli lastpass-cli Application openstack-dashboard openstack-dashboard #N/A python3-horizon openstack-dashboard #N/A ovirt-engine ovirt-engine oVirt ovirt-engine-setup-plugin-ovirt-engine ovirt-engine oVirt ovirt-provider-ovn ovirt-provider-ovn oVirt ovirt-engine-backend ovirt-engine oVirt ovirt-engine-dbscripts ovirt-engine oVirt ovirt-engine-dwh ovirt-engine-dwh oVirt ovirt-engine-dwh-grafana-integration-setup ovirt-engine-dwh oVirt ovirt-engine-dwh-setup ovirt-engine-dwh oVirt ovirt-engine-restapi ovirt-engine oVirt ovirt-engine-setup ovirt-engine oVirt ovirt-engine-setup-plugin-cinderlib ovirt-engine oVirt ovirt-engine-setup-plugin-imageio ovirt-engine oVirt ovirt-engine-setup-plugin-vmconsole-proxy-helper ovirt-engine oVirt ovirt-engine-tools ovirt-engine oVirt ovirt-engine-webadmin-portal ovirt-engine oVirt ovirt-engine-ui-extensions ovirt-engine-ui-extensions oVirt ovirt-engine-vmconsole-proxy-helper ovirt-engine oVirt ovirt-provider-ovn-driver ovirt-provider-ovn oVirt python3-graphviz python-graphviz sig-python-modules python3-ironic-ui python-ironic-ui sig-openstack python3-mitmproxy python-mitmproxy sig-python-modules python3-muranoclient python-muranoclient sig-openstack python3-neutron-tempest-plugin python-neutron-tempest-plugin sig-openstack python3-os-xenapi-tests python-os-xenapi sig-openstack python3-pep517 python-pep517 sig-python-modules python3-pip-api python-pip-api sig-openstack python3-requirementslib python-requirementslib sig-openstack python3-senlinclient python-senlinclient sig-openstack python3-trove-tempest-plugin python-trove-tempest-plugin sig-openstack ukui ukui-desktop-environment sig-UKUI ukui-desktop-environment ukui-desktop-environment sig-UKUI ukui-desktop-environment-core ukui-desktop-environment sig-UKUI kylin-music kylin-music sig-UKUI ------ BR 陈亚强（openEuler release management sig）

1 0

openEuler Summit 2021 诚挚的邀请您提交演讲议题、成为共建单位、贡献展示方案
by Marketing openEuler 29 Sep '21

29 Sep '21

openEuler Summit 是由欧拉开源社区举办的开发者峰会。全新升级后的首场峰会将于 11 月10日在北京举行。 openEuler 从服务器操作系统，升级为数字基础设施的操作系统，支持 IT、CT、OT 等数字基础设施全场景，覆盖服务器、云、边、嵌入式等各种形态的需求。伴随 openEuler 21.09 的发布，openEuler 已经包含了服务器、云原生、边缘计算和嵌入式的四大应用场景。 openEuler 通过开源开放，不断探索科技创新的边界。开发者、用户、社区贡献者、软件爱好者在 openEuler Summit 汇聚，共同解读 openEuler 的最新版，探讨未来的技术路线，让技术、生态、商业在这里产生奇妙的化学反应。 *本次峰会旨在推动 openEuler 在多样性计算、云计算、边缘计算、嵌入式等技术方向的持续探索和创新。* 开源是一种态度、分享是一种精神。Call for Speaker、Call for Sponsor、Call for Demo 现已全面开放报名。大会报名通道同步开启。 *我们诚挚的邀请您提交演讲议题、发表联合演讲、成为共建单位、贡献展示方案、参与社区建设。* - *大会官网：*https://www.openeuler.org/zh/interaction/summit-list/summit2021/ - *Call for Speaker：*https://shimowendang.com/forms/X6X9jj9KPcdQwVr8/fill - *Call for Sponsor：*https://shimowendang.com/forms/k76zTLKvumYwRdsP/fill - *Call for Demo：*https://shimowendang.com/forms/LjHs8JlsLSsW92kl/fill

1 0

关于gazelle/gazelle-cni 的源码与项目问题
by TJU 刘昊 20 Sep '21

20 Sep '21

openeuler的各位前辈你们好：   我是天津大学计算机学院的一名硕士研究生（研一），目前的主攻方向为高性能容器网络，在gitee上浏览到了Gazelle-cni的仓库，看到了一些规划，对此很感兴趣。但我未在官网/github查看到有关项目，因此无法深入了解。想请教一下项目有关资料，以及能否/如何成为一名开发者。    祝：BUG越少，头发不掉

1 0

openEuler 任务打榜赛6月21日-6月28日周榜单来啦
by Marketing openEuler 29 Jun '21

29 Jun '21

openEuler 任务打榜赛6月21日-6月28日周榜单来啦，快来看看有没有你的名字吧。这里提醒已领取赛题但是还没有加群的小伙伴赶紧联系小助手加群呀。好啦~，下面让我们看一下有哪些开发者上榜吧！ gitee用户账号积分值解决issue/pr数量 yaozc701 20 4 dada5208 16 5 shuyao13 14 4 houlibao 12 3 liuerwuliu 12 3 hw999666 8 2 gc7500 8 2 weidongkl 6 1 shao1112 6 2 wss1235 2 1 恭喜以上开发者，请联系小助手领奖。没有上榜的小伙伴不要灰心，请再接再历。周榜、月榜前十名均有奖励，期待在榜单上早点见到你。添加小助手微信（SoftCorePro）回复“*任务打榜赛*”进入交流群 *了解更多* - 官网：https://openeuler.org/zh/interaction/hdc/2021-developer.html - 我要报名： https://competition.huaweicloud.com/information/1000041420/introduction - 我要做题： https://gitee.com/organizations/src-openeuler/issues?assignee_id=&author_id…

1 0

快来看你是否上榜~！openEuler 任务打榜赛5月榜单出炉
by Marketing openEuler 24 Jun '21

24 Jun '21

经过一个月的角逐，openEuler 任务打榜赛5月榜单来啦。在这一个月的时间里，开发者参加任务打榜赛的热情高涨：总计有*38*人领取*118*道赛题，赛道交流群成员*70*个，这里 *提醒领取赛题但是还没有加群的小伙伴赶紧联系小助手加群*呀。好啦~，下面让我们看一下5月份有哪些开发者上榜吧！ gitee用户账号 gitee邮箱积分值解决issue/pr数量 li-kaiyuan66666 likaiyuan7(a)huawei.com 6 1 yanxiaobing2020 yanxiaobing(a)huawei.com 2 1 zhu-yuncheng zhuyuncheng(a)huawei.com 6 1 polite2anyone zhangyao05(a)outlook.com 10 2 yaozc701 yaozc7(a)chinaunicom.cn 18 2 恭喜以上开发者，请中奖的开发者联系小助手*领奖*。没有上榜的小伙伴不要灰心请再接再历，周榜、月榜前十名均有奖励，期待在榜单上早点见到你。让我们共同期待6月的榜单。 [image: image.png] 添加小助手微信回复“*任务打榜赛*”进入交流群 *了解更多* - 官网：https://openeuler.org/zh/interaction/hdc/2021-developer.html - 我要报名： https://competition.huaweicloud.com/information/1000041420/introduction - 我要做题： https://gitee.com/organizations/src-openeuler/issues?assignee_id=&author_id…

1 1

完成任务，获得荣誉，openEuler 社区的这项比赛有点逆天！
by Marketing openEuler 27 May '21

27 May '21

先说比赛规则独立开发者参赛 *做题得分* *每周结算* 这是任务打榜赛不满足？来看一下*特性命题赛*？独立开发者组队参赛区域赛、半决赛、总决赛过五关斩六将谁可以独占鳌头？你将是*社区贡献者* *你的 ID* 会被铭刻在社区还有*“一”点奖金* [image: WechatIMG16.jpeg]

1 0

Fwd: openEuler Developer Day 启动大会招募环节，报名通道同步开启！
by Marketing openEuler 17 May '21

17 May '21

openEuler 社区的开发者：您好！ openEuler Developer Day 2021 将于*6**月10日*在北京举行。本次大会是由 openEuler 社区发起，主要面向签署了 CLA的核心开发者、南北向生态厂商以及核心用户的一场技术盛会，旨在推动 openEuler 社区在多样性计算、云原生全栈、全场景协同等技术方向的持续探索和创新。 *开放招募* openEuler Developer Day 正式开放招募环节：*Call for Speaker* <https://shimo.im/forms/KgXxt8JCYKYtVXHx/fill>、*Call for Sponsor* <https://shimo.im/forms/vwCC68q3pQvvR3Yc/fill>、*Call for SIG* <https://shimo.im/forms/x6vXyW8QHCGK9QJD/fill>、*Call for Demo* <https://shimo.im/forms/PQTvWKjHgg96DjD8/fill> 欢迎 openEuler 社区的开发者提交以上四个方面的材料。 [image: 截屏2021-05-13 下午8.12.43.png] *大会亮点* 这是一场大型的面向 openEuler 社区开发者的技术交流会议。在现场共同探讨*热点技术方向*和*如何参与社区贡献*，通过大会*公开接收用户需求*，*完成版本规划*。 *技术委员会*、*品牌委员会*、*用户委员会*、*20个 SIG 组*会同期举办*开放工作会议**（仅限签署社区 CLA 的开发者参加）*。技术委员会主席给大家解读 *openEuler 21.03*，发布下个社区版的*技术定位*，分享社区创新思路。来自互联网、金融、运营商的客户分享成功的应用实践经验。开源圆桌中，客户、伙伴、厂商、研究机构一同探究开源软件供应链的意义和风险，开源模式如何推动独立演进操作系统技术的发展。更有开发者心心念念的 *Party* 心动不如行动，赶紧来报名参会 <https://e-campaign.huawei.com/m/mIzQFr>吧！！！

1 0

欢迎各位报例会议题==>答复: [Dev] high-performance-network 例会
by Luzhihao (luzhihao, Euler) 12 Jan '21

12 Jan '21

发件人: openEuler conference [mailto:public@openeuler.io] 发送时间: 2021年1月12日 16:57 主题: [Dev] high-performance-network 例会您好！ openEuler sig-high-performance-network SIG 邀请您参加 2021-01-14 19:00 召开的ZOOM会议会议主题：high-performance-network 例会会议内容：高性能网络sig例会会议链接：https://zoom.us/j/91509801764?pwd=RzJNZFQwR29OdkFNYW9LcDJOVWp2QT09 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the ZOOM conference will be held at 2021-01-14 19:00, The subject of the conference is high-performance-network 例会, Summary: 高性能网络sig例会 You can join the meeting at https://zoom.us/j/91509801764?pwd=RzJNZFQwR29OdkFNYW9LcDJOVWp2QT09. More information<https://openeuler.org/zh/>

1 0

会议纪要=>答复: [Dev] sig-high-performance-network 例会
by Luzhihao (luzhihao, Euler) 31 Dec '20

31 Dec '20

首先欢迎江苏紫金山实验室同学加入高性能网络sig~ 祝本sig以及openEuler社区同仁们元旦快乐！本期进展： 1． Gazelle CNI项目进展：– 陆志浩/黎明/长冶 a) 继续细分场景，已明确Gazelle CNI目标就是加速云原生 Service Mesh L7网络。 b) 已经完成istio数据面envoy部件使用的网络相关的POSIX接口范围搜集。 2． OCNF项目进展：– 刘忻 a) 已经完成OKD环境搭建，参考OKD作为OCNF项目的设计输入。 b) CNI选型工作暂停，待与下游厂商交流后，再考虑选型方案。 3． Tarsier项目进展：– 金荣（西邮团队） a) 完成部分技术（包括DB、编程语言等）选型工作，部分内容有待调整。 b) 近期会将技术选型结果，项目路线图上传至项目内。 4．紫金山实验室高性能CNI项目介绍：– 沈洋/于兆国（紫金山实验室团队） a) 首次介绍了紫金山实验室自研的高性能CNI，尤其其中的LB能力。 b) 目前该CNI项目已经处于ready状态，希望在openEuler平台上找到云原生客户场景（尤其是信创类客户），并考虑在高性能网络sig内开源该项目。下一步工作： 1． Gazelle CNI项目：– 陆志浩/黎明/长冶 a) 熟悉bazel构建方式，尝试构建Envoy，将Gazelle库构建进Envoy部件。 2． OCNF项目：– 刘忻/黎明 a) OCNF详细设计工作。 -- 刘忻 b) Additional CNI设计工作 -- 黎明 3． Tarsier项目：– 金荣（西邮团队） a) 完成框架设计后（需要与openEuler导师核对），开始模块内详细设计工作。 4．紫金山实验室高性能CNI项目介绍：– 沈洋/于兆国（紫金山实验室团队） a) 继续保持sig内交流，寻找下游厂商客户，并讨论项目开源的具体操作细节。 5．云原生下游厂商需求讨论 -- 陆志浩发件人: openEuler conference [mailto:public@openeuler.io] 发送时间: 2020年12月25日 19:56 收件人: dev(a)openeuler.org; sig-high-performance-network(a)epeneuler.org 主题: [Dev] sig-high-performance-network 例会您好！ openEuler sig-high-performance-network SIG 邀请您参加 2020-12-31 19:00 召开的ZOOM会议会议主题：sig-high-performance-network 例会会议内容：前期工作总结后期工作讨论会议链接：https://zoom.us/j/94041283864?pwd=YXBPckpISmZ3L0g5bklzRmJqL0diUT09 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the ZOOM conference will be held at 2020-12-31 19:00, The subject of the conference is sig-high-performance-network 例会, Summary: 前期工作总结后期工作讨论 You can join the meeting at https://zoom.us/j/94041283864?pwd=YXBPckpISmZ3L0g5bklzRmJqL0diUT09. More information<https://openeuler.org/zh/>

1 0

会议纪要==>答复: sig-high-performance-network regular meeting
by Luzhihao (luzhihao, Euler) 17 Dec '20

17 Dec '20

本期进展： 1． Gazelle CNI项目进展：– 陆志浩/黎明/长冶 a) 确定了两个场景：IO intensive APP独立部署、IO intensive /Legacy APP混合部署。优先落地独立部署场景。 b) XDP方案完成 IO intensive APP独立部署方案设计。 c) DPDK方案确定技术路线，优先将原Gazelle项目在K8S环境部署运行成功。 2． OCNF项目进展：– 刘忻 a) 初步选型OVN-kubernetes 作为云原生应用平台的default CNI。 b) OCNF CRD设计中。 3． Tarsier项目进展：– 金荣（西邮团队） a) 已完成项目计划，软件框架设计。 b) 完成了一些开源项目的借鉴参考，并完成了一个原型验证工作。下一步工作： 1． Gazelle CNI项目：– 陆志浩/黎明/长冶 a) openEuler范围内明确应用场景，并推动Gazelle项目开源。 b) Gazelle CNI完成DPDK方案演示（无上层应用）。 2． OCNF项目：– 刘忻 a) 完成OKD环境搭建，并尝试安装OVN-Kubernetes，分析其CRD，作为OCNF operator CRD设计的输入。 3． Tarsier项目：– 金荣（西邮团队） a) 将已完成的路标、设计工作提交PR至openEuler项目内。 b) 确定详细的技术路线，包括详细方案设计、编程语言、基础软件（DB、Log等）。发件人: openEuler conference via High-performance-network [mailto:high-performance-network@openeuler.org] 发送时间: 2020年12月16日 19:08 收件人: high-performance-network(a)openeuler.org; dev(a)openeuler.org; tc(a)openeuler.org 主题: [High-performance-network] sig-high-performance-network regular meeting 您好！ openEuler sig-high-performance-network SIG 邀请您参加 2020-12-17 20:00 召开的ZOOM会议会议主题：sig-high-performance-network regular meeting 会议内容：1. sig成员前期工作审视 2. 下一步计划与分工会议链接：https://zoom.us/j/99700036821?pwd=aS9SMEpJbnJQYnJVNThPWjdoc21xdz09 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the ZOOM conference will be held at 2020-12-17 20:00, The subject of the conference is sig-high-performance-network regular meeting, Summary: 1. sig成员前期工作审视 2. 下一步计划与分工 You can join the meeting at https://zoom.us/j/99700036821?pwd=aS9SMEpJbnJQYnJVNThPWjdoc21xdz09. More information<https://openeuler.org/zh/>

1 0

sig-high-performance-network regular meeting
by openEuler conference 16 Dec '20

16 Dec '20

1 0

西邮的同学你们先研究下这个开源项目，看看对我们要做的工作是否有帮助
by Luzhihao (luzhihao, Euler) 11 Dec '20

11 Dec '20

https://github.com/ntop/libebpfflow ---------------------------------------------------------------- 陆志浩 13913964603 华为技术有限公司，庞家莱实验室 openEuler 高性能网络sig ：high-performance-network(a)openeuler.org openEuler社区：https://openeuler.org/zh/

1 0

会议纪要==>答复: [Tc] sig-high-performance-network regular meeting
by Luzhihao (luzhihao, Euler) 09 Dec '20

09 Dec '20

与会人：好多好多。。。记不清了本期进展： 1、gazelle-cni XDP方案设计进行中，基本完成数据面的设计工作，管理面设计工作待进行。 2、OCNF 方案设计，完成OCNF 粗粒度框架性设计工作，详细设计待进行。 3、内核BPF patch推送，目前只完成一批patch推送。下一步计划： 1、gazelle-cni 项目整体的roadmap/整体设计/博客宣传 -- 吴长冶 2、gazelle-cni DPDK方案设计 -- 黄黎明 3、完成OCNF详细设计，包括default cni选型，CRD定义 -- 刘欣 4、输出BPF patch推送工作计划 -- 朱迪 5、云原生应用场景可视化运维项目启动 -- 梁金荣（西邮） 6、云原生网络数据面性能分析输出博客 -- 陆志浩发件人: openEuler conference [mailto:public@openeuler.io] 发送时间: 2020年12月3日 9:37 收件人: high-performance-network(a)openeuler.org; dev(a)openeuler.org; tc(a)openeuler.org 主题: [Tc] sig-high-performance-network regular meeting 您好！ openEuler sig-high-performance-network SIG 邀请您参加 2020-12-03 19:00 召开的ZOOM会议会议主题：sig-high-performance-network regular meeting 会议内容：1. sig成员前期工作审视 2. 下一步计划与分工会议链接：https://zoom.us/j/93525169356?pwd=RW43MEFnc2NCSmFIY0JXMnZTcDZTUT09 更多资讯尽在：https://openeuler.org/zh/ Hello! openEuler sig-high-performance-network SIG invites you to attend the ZOOM conference will be held at 2020-12-03 19:00, The subject of the conference is sig-high-performance-network regular meeting, Summary: 1. sig成员前期工作审视 2. 下一步计划与分工 You can join the meeting at https://zoom.us/j/93525169356?pwd=RW43MEFnc2NCSmFIY0JXMnZTcDZTUT09. More information<https://openeuler.org/zh/>

1 0

openEuler 高校开发者大赛报名链接
by Luzhihao (luzhihao, Euler) 08 Dec '20

08 Dec '20

https://www.oschina.net/2020-openeuler/ [cid:image001.png@01D6CD54.36E91440] ---------------------------------------------------------------- 陆志浩 13913964603 华为技术有限公司，庞家莱实验室 openEuler 高性能网络sig ：high-performance-network(a)openeuler.org openEuler社区：https://openeuler.org/zh/

1 0

@西邮同学：openEuler提PR参考手册
by Luzhihao (luzhihao, Euler) 03 Dec '20

03 Dec '20

https://openeuler.org/zh/community/contribution/ 创建一个项目，可以参考：https://gitee.com/openeuler/community/pulls/1313 ---------------------------------------------------------------- 陆志浩 13913964603 华为技术有限公司，庞家莱实验室 openEuler 高性能网络sig ：high-performance-network(a)openeuler.org openEuler社区：https://openeuler.org/zh/

1 0

答复: openEuler 赛题咨询
by Luzhihao (luzhihao, Euler) 03 Dec '20

03 Dec '20

很高兴收到您的提问。微服务API可视化要提取的信息准确的来说来源两部分：1）kernel 内进程（实际就是微服务程序本身）执行上下文，比如其发起的TCP链接信息。2）K8S Deployment信息。最后将两者信息结合在一起，形成流路径拓扑绘制。这里面我们应该不限制微服务执行RPC是rest，还是grpc，或者其他类型。 ---------------------------------------------------------------- 陆志浩 13913964603 华为技术有限公司，庞家莱实验室 openEuler 高性能网络sig ：high-performance-network(a)openeuler.org openEuler社区：https://openeuler.org/zh/ 发件人: hzs98(a)mail.ustc.edu.cn [mailto:hzs98@mail.ustc.edu.cn] 发送时间: 2020年12月3日 16:09 收件人: Luzhihao (luzhihao, Euler) <luzhihao(a)huawei.com> 主题: openEuler 赛题咨询卢老师你好: 我想请问一下, 微服务API性能信息是从 eBPF 中提取还是通过 API 网关服务器中的 API 信息主动发送 API测试请求去测. 这些 API 只包含微服务系统内部的调用不包含客户端的调用吗. 然后这些微服务间 API 接口是 HTTP 还是 REST , 另外实际的微服务生产环境可以用来开发, 部署和测试代码吗?

1 0

答复: 2020 openEuler 高校开发者大赛-容器网络可视化——西邮梁金荣
by Luzhihao (luzhihao, Euler) 03 Dec '20

03 Dec '20

非常欢迎老师/同学能够参与到openEuler社区活动中来。请同学/老师们订阅下社区邮件，如已订阅请忽略，后续讨论直接基于这个邮件列表讨论。然后我介绍下容器网络可视化（也可以叫云原生场景可视化）这个项目现状及初衷。项目初衷：我们希望能够在云原生场景，针对容器业务实现微服务API流的可视化能力，当然这是第一步，最终目标是实现微服务API全栈可视化。行业内现在有一些成熟开源项目，比如istio、sysdig、cilium（hubble）等。其中sysdig、hubble这类项目可以作为我们重点参考对象，其原理都是通过内核BPF挂hook解析进程系统调用，观察容器内微服务网络通信事件。将内核观察到的数据与K8S Deployment部署信息结合，最后通过Prometheus展示出来。项目现状：目前还处于萌芽状态，只是有基本思路，希望在社区孵化一个原型出来，同时能够吸引更多这方面的爱好者。 openEuler社区的高性能网络sig里面有eBPF、BCC等方面的技术专家，可以与大家一起设计这个原型项目。 PS：邮件列表地址：https://openeuler.org/zh/community/mailing-list/ 1．一般社区需求讨论是订阅 dev(a)openeuler.org<mailto:dev@openeuler.org> 2．高性能网络sig 是订阅 high-performance-network(a)openeuler.org<mailto:high-performance-network@openeuler.org> 发件人: ljrcore [mailto:ljrcore@126.com] 发送时间: 2020年12月2日 12:40 收件人: Luzhihao (luzhihao, Euler) <luzhihao(a)huawei.com> 主题: 2020 openEuler 高校开发者大赛-容器网络可视化——西邮梁金荣陆老师，您好，我是西邮Linux内核团队的梁金荣，报名参加 2020 openEuler 高校开发者大赛，选题为“容器网络可视化”。我们团队研究方向是Linux内核，目前具备的基础： · 熟悉基本的Linux命令 · 熟悉Linux内核知识，分析过Linux内核网络协议栈源码，我写的相关博客： http://kerneltravel.net/categories/%E5%86%85%E6%A0%B8%E7%BD%91%E7%BB%9C/ · 熟悉eBPF/bcc，编写bcc程序提取过内核网络数据，我写的相关博客： http://kerneltravel.net/categories/ebpf/ · 熟悉c，python语言，了解go语言 · 了解kubernetes基本知识，使用过docker 如果可以的话，您可以回复一下您的微信，我们进一步交流和明确选题“容器网络可视化”，非常希望得到陆老师的指导，谢谢老师。 --------------------------- 西邮Linux内核团队梁金荣微信号：ljrcore [https://mail-online.nosdn.127.net/qiyelogo/defaultAvatar.png] ljrcore ljrcore(a)126.com<mailto:ljrcore@126.com> 签名由网易邮箱大师<https://mail.163.com/dashi/dlpro.html?from=mail81> 定制

1 0

sig-high-performance-network regular meeting
by openEuler conference 03 Dec '20

03 Dec '20

1 0

sig-high-performance-network regular meeting
by openEuler conference 20 Nov '20

20 Nov '20

2 1

会议纪要 //回复：【Meeting Notice】sig-high-performance-network regular meeting Time: 2020-11-05 19:00-20:00
by Peanut_Huang 09 Nov '20

09 Nov '20

与会人：Mr.lu, hubble_zhu, peanut_huang, gao_xingwang, yuan_xin, wu_changye, zhao_wei, liu_xin 前期进展： 1. 将polycube相关工具包推到openEuler上     pyang已合入社区，pyang-swagger待本地构建验证 -- gao_xiingwang     polycube-codegen待本地构建验证 -- peanut_huang     xdp-tools已合入社区 -- hubble_zhu 下一步计划： 1. 建议尽快完成polycube软件平台的生态构建     pyang-swagger -- gao_xiingwang     polycube-codegen -- peanut_huang 2. 建议在openEuler上将polycube开发平台初步运行起来 -- hubble_zhu 3. 建议构建openEuler CNI能力，分以下几步走：     1）引入multus-cni（具备良好的cni扩展能力），构造openEuler基本cni能力；     2）基于Gazelle项目，实现 Gazelle CNI解决方案，面向边缘场景PoD提供高性能协议栈能力；     3）基于polycube项目，实现高性能通用CNI解决方案。 ------------------ 原始邮件 ------------------ 发件人: "Meeting Book" <uMeeting(a)huawei.com>; 发送时间: 2020年10月29日(星期四) 晚上10:14 收件人: "Peanut_Huang"<hlm3280(a)qq.com>; 主题: 【Meeting Notice】sig-high-performance-network regular meeting Time: 2020-11-05 19:00-20:00 Topic sig-high-performance-network regular meeting Time 2020-11-05 19:00-20:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 962 613 066   Convener 黄黎明   Agenda 1. sig成员前期工作审视 2. 下一步计划与分工   Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载 If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download

1 0

sig-high-performance-network例会
by openEuler conference 03 Nov '20

03 Nov '20

1 0

会议纪要 //回复：【Meeting Notice】sig-high-performance-network regular meeting Time: 2020-10-15 19:00-20:00
by Peanut_Huang 19 Oct '20

19 Oct '20

与会人：Mr.lu, hubble_zhu, peanut_huang, gao_xiingwang, yuan_xin, xu_changye 【会议纪要】前期进展： 1. polycube框架已经成功在openEuler上运行，相关修改等待合入社区 -- liu_xin 2. 将polycube相关工具包推到openEuler上     swagger-codegen已在本地成功构建和运行，待提交合入社区 -- peanut_huang     pyang-swagger依赖pyang，正在验证pyang的构建 -- gao_xiingwang 下一步计划： 1. 建议尽快将polycube相关工具包推到openEuler上     pyang-swagger、pyang -- gao_xiingwang     polycube-codegen   -- peanut_huang     xdp-tools        -- hubble_zhu 2. 建议补充部分高性能网络sig的愿景材料 -- Mr.lu ------------------ 原始邮件 ------------------ 发件人: "Peanut_Huang" <hlm3280(a)qq.com>; 发送时间: 2020年10月14日(星期三) 晚上7:25 收件人: "high-performance-network"<high-performance-network(a)openeuler.org>;"tc"<tc(a)openeuler.org>;"dev"<dev(a)openeuler.org>; 主题: 【Meeting Notice】sig-high-performance-network regular meeting Time: 2020-10-15 19:00-20:00 Topic sig-high-performance-network regular meeting Time 2020-10-15 19:00-20:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 985 033 429   Convener Peanut_Huang Agenda 1.sig成员前期工作审视 2.下一步工作和计划 Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载 If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download

1 0

test
by Hubble_Zhu 15 Oct '20

15 Oct '20

test

1 3

【Meeting Notice】sig-high-performance-network regular meeting Time: 2020-10-15 19:00-20:00
by Peanut_Huang 14 Oct '20

14 Oct '20

Topic sig-high-performance-network regular meeting Time 2020-10-15 19:00-20:00((UTC+08:00)Beijing)   Join Conference Join (External) >> Meeting ID 985 033 429   Convener Peanut_Huang Agenda 1.sig成员前期工作审视 2.下一步工作和计划 Tips: Dial the access number to join conference 注：仅支持部分国家和地区。( Only some countries and regions are supported.) 如果加入会议提示“会议已结束或会议号不存在”，请在官网下载最新版本入会。立即下载 If a message is displayed, indicating that the meeting has ended or the meeting ID does not exist, download the latest meeting client and try again.Download

1 0

test
by hlm3280 14 Oct '20

14 Oct '20

test

1 0

test
by Peanut_Huang 14 Oct '20

14 Oct '20

/test

1 1

hello
by Hubble_Zhu 19 Sep '20

19 Sep '20

hello

1 1