event/dlb2: add support for single 512B write of 4 QEs
PATCH v5 1/1 event/dlb2: add support for single 512B write of 4 QEs
On Xeon, 512b accesses are available, so movdir64 instruction is able to perform 512b read and write to DLB producer port. In order for movdir64 to be able to pull its data from store buffers (store-buffer-forwarding) (before actual write), data should be in single 512b write format. This commit add change when code is built for Xeon with 512b AVX support to make single 512b write of all 4 QEs instead of 4x64b writes.
===
Changes since V4:
1) Add build-time control for avx512 support to meson.buildi, based on implementation found in lib/acl/meson.build
2) Add rte_vect_get_max_simd_bitwidth runtime check before using avx512 instructions
Changes since V3:
1) Renamed dlb2_noavx512.c to dlb2_sve.c, and fixed up meson.build for new file name.
Changes since V1:
1) Split out dlb2_event_build_hcws into two implementations, one that uses AVX512 instructions, and one that does not. Each implementation is in its own source file in order to avoid build errors if the compiler does not support the newer AVX512 instructions.
2) Update meson.build to and pull in appropriate source file based on whether the compiler supports AVX512VL
3) Check if target supports AVX512VL, and use appropriate implementation based on this runtime check.
--- drivers/event/dlb2/dlb2.c | 208 +----------------------- drivers/event/dlb2/dlb2_avx512.c | 267 +++++++++++++++++++++++++++++++ drivers/event/dlb2/dlb2_priv.h | 10 ++ drivers/event/dlb2/dlb2_sve.c | 219 +++++++++++++++++++++++++ drivers/event/dlb2/meson.build | 53 ++++++ 5 files changed, 556 insertions(+), 201 deletions(-) create mode 100644 drivers/event/dlb2/dlb2_avx512.c create mode 100644 drivers/event/dlb2/dlb2_sve.c
drivers/event/dlb2/dlb2.c +7 -201
@@ -1861,6 +1861,13 @@ dlb2_eventdev_port_setup(struct rte_eventdev *dev, dev->data->ports[ev_port_id] = &dlb2->ev_ports[ev_port_id]; +#ifdef CC_AVX512_SUPPORT +if (rte_cpu_get_flag_enabled (RTE_CPUFLAG_AVX512VL ) && +rte_vect_get_max_simd_bitwidth () >=RTE_VECT_SIMD_512 ) + ev_port->qm_port.use_avx512 = true; +else + ev_port->qm_port.use_avx512 = false; +#endif return 0 ; }
@@ -2457,21 +2464,6 @@ dlb2_eventdev_start(struct rte_eventdev *dev)return 0 ; } -static uint8_t cmd_byte_map[DLB2_NUM_PORT_TYPES ][DLB2_NUM_HW_SCHED_TYPES ] = { - { -/* Load-balanced cmd bytes */ - [RTE_EVENT_OP_NEW ] =DLB2_NEW_CMD_BYTE , - [RTE_EVENT_OP_FORWARD ] =DLB2_FWD_CMD_BYTE , - [RTE_EVENT_OP_RELEASE ] =DLB2_COMP_CMD_BYTE , - }, - { -/* Directed cmd bytes */ - [RTE_EVENT_OP_NEW ] =DLB2_NEW_CMD_BYTE , - [RTE_EVENT_OP_FORWARD ] =DLB2_NEW_CMD_BYTE , - [RTE_EVENT_OP_RELEASE ] =DLB2_NOOP_CMD_BYTE , - }, -}; -static inline uint32_t dlb2_port_credits_get (struct dlb2_port *qm_port,enum dlb2_hw_queue_types type)
@@ -2666,192 +2658,6 @@ dlb2_construct_token_pop_qe(struct dlb2_port *qm_port, int idx) qm_port->owed_tokens =0 ; } -static inline void -dlb2_event_build_hcws (struct dlb2_port *qm_port, -const struct rte_event ev[], -int num, -uint8_t *sched_type, -uint8_t *queue_id) -{ -struct dlb2_enqueue_qe *qe; -uint16_t sched_word[4 ]; -__m128i sse_qe[2 ]; -int i; - - qe = qm_port->qe4; - - sse_qe[0 ] =_mm_setzero_si128 (); - sse_qe[1 ] =_mm_setzero_si128 (); - -switch (num) { -case 4 : -/* Construct the metadata portion of two HCWs in one 128b SSE -* register. HCW metadata is constructed in the SSE registers -* like so: -* sse_qe[0][63:0]: qe[0]'s metadata -* sse_qe[0][127:64]: qe[1]'s metadata -* sse_qe[1][63:0]: qe[2]'s metadata -* sse_qe[1][127:64]: qe[3]'s metadata -*/ - -/* Convert the event operation into a command byte and store it -* in the metadata: -* sse_qe[0][63:56] = cmd_byte_map[is_directed][ev[0].op] -* sse_qe[0][127:120] = cmd_byte_map[is_directed][ev[1].op] -* sse_qe[1][63:56] = cmd_byte_map[is_directed][ev[2].op] -* sse_qe[1][127:120] = cmd_byte_map[is_directed][ev[3].op] -*/ -#define DLB2_QE_CMD_BYTE 7 - sse_qe[0 ] =_mm_insert_epi8 (sse_qe[0 ], - cmd_byte_map[qm_port->is_directed][ev[0 ].op], -DLB2_QE_CMD_BYTE ); - sse_qe[0 ] =_mm_insert_epi8 (sse_qe[0 ], - cmd_byte_map[qm_port->is_directed][ev[1 ].op], -DLB2_QE_CMD_BYTE +8 ); - sse_qe[1 ] =_mm_insert_epi8 (sse_qe[1 ], - cmd_byte_map[qm_port->is_directed][ev[2 ].op], -DLB2_QE_CMD_BYTE ); - sse_qe[1 ] =_mm_insert_epi8 (sse_qe[1 ], - cmd_byte_map[qm_port->is_directed][ev[3 ].op], -DLB2_QE_CMD_BYTE +8 ); - -/* Store priority, scheduling type, and queue ID in the sched -* word array because these values are re-used when the -* destination is a directed queue. -*/ - sched_word[0 ] =EV_TO_DLB2_PRIO (ev[0 ].priority) <<10 | - sched_type[0 ] <<8 | - queue_id[0 ]; - sched_word[1 ] =EV_TO_DLB2_PRIO (ev[1 ].priority) <<10 | - sched_type[1 ] <<8 | - queue_id[1 ]; - sched_word[2 ] =EV_TO_DLB2_PRIO (ev[2 ].priority) <<10 | - sched_type[2 ] <<8 | - queue_id[2 ]; - sched_word[3 ] =EV_TO_DLB2_PRIO (ev[3 ].priority) <<10 | - sched_type[3 ] <<8 | - queue_id[3 ]; - -/* Store the event priority, scheduling type, and queue ID in -* the metadata: -* sse_qe[0][31:16] = sched_word[0] -* sse_qe[0][95:80] = sched_word[1] -* sse_qe[1][31:16] = sched_word[2] -* sse_qe[1][95:80] = sched_word[3] -*/ -#define DLB2_QE_QID_SCHED_WORD 1 - sse_qe[0 ] =_mm_insert_epi16 (sse_qe[0 ], - sched_word[0 ], -DLB2_QE_QID_SCHED_WORD ); - sse_qe[0 ] =_mm_insert_epi16 (sse_qe[0 ], - sched_word[1 ], -DLB2_QE_QID_SCHED_WORD +4 ); - sse_qe[1 ] =_mm_insert_epi16 (sse_qe[1 ], - sched_word[2 ], -DLB2_QE_QID_SCHED_WORD ); - sse_qe[1 ] =_mm_insert_epi16 (sse_qe[1 ], - sched_word[3 ], -DLB2_QE_QID_SCHED_WORD +4 ); - -/* If the destination is a load-balanced queue, store the lock -* ID. If it is a directed queue, DLB places this field in -* bytes 10-11 of the received QE, so we format it accordingly: -* sse_qe[0][47:32] = dir queue ? sched_word[0] : flow_id[0] -* sse_qe[0][111:96] = dir queue ? sched_word[1] : flow_id[1] -* sse_qe[1][47:32] = dir queue ? sched_word[2] : flow_id[2] -* sse_qe[1][111:96] = dir queue ? sched_word[3] : flow_id[3] -*/ -#define DLB2_QE_LOCK_ID_WORD 2 - sse_qe[0 ] =_mm_insert_epi16 (sse_qe[0 ], - (sched_type[0 ] ==DLB2_SCHED_DIRECTED ) ? - sched_word[0 ] : ev[0 ].flow_id, -DLB2_QE_LOCK_ID_WORD ); - sse_qe[0 ] =_mm_insert_epi16 (sse_qe[0 ], - (sched_type[1 ] ==DLB2_SCHED_DIRECTED ) ? - sched_word[1 ] : ev[1 ].flow_id, -DLB2_QE_LOCK_ID_WORD +4 ); - sse_qe[1 ] =_mm_insert_epi16 (sse_qe[1 ], - (sched_type[2 ] ==DLB2_SCHED_DIRECTED ) ? - sched_word[2 ] : ev[2 ].flow_id, -DLB2_QE_LOCK_ID_WORD ); - sse_qe[1 ] =_mm_insert_epi16 (sse_qe[1 ], - (sched_type[3 ] ==DLB2_SCHED_DIRECTED ) ? - sched_word[3 ] : ev[3 ].flow_id, -DLB2_QE_LOCK_ID_WORD +4 ); - -/* Store the event type and sub event type in the metadata: -* sse_qe[0][15:0] = flow_id[0] -* sse_qe[0][79:64] = flow_id[1] -* sse_qe[1][15:0] = flow_id[2] -* sse_qe[1][79:64] = flow_id[3] -*/ -#define DLB2_QE_EV_TYPE_WORD 0 - sse_qe[0 ] =_mm_insert_epi16 (sse_qe[0 ], - ev[0 ].sub_event_type <<8 | - ev[0 ].event_type, -DLB2_QE_EV_TYPE_WORD ); - sse_qe[0 ] =_mm_insert_epi16 (sse_qe[0 ], - ev[1 ].sub_event_type <<8 | - ev[1 ].event_type, -DLB2_QE_EV_TYPE_WORD +4 ); - sse_qe[1 ] =_mm_insert_epi16 (sse_qe[1 ], - ev[2 ].sub_event_type <<8 | - ev[2 ].event_type, -DLB2_QE_EV_TYPE_WORD ); - sse_qe[1 ] =_mm_insert_epi16 (sse_qe[1 ], - ev[3 ].sub_event_type <<8 | - ev[3 ].event_type, -DLB2_QE_EV_TYPE_WORD +4 ); - -/* Store the metadata to memory (use the double-precision -* _mm_storeh_pd because there is no integer function for -* storing the upper 64b): -* qe[0] metadata = sse_qe[0][63:0] -* qe[1] metadata = sse_qe[0][127:64] -* qe[2] metadata = sse_qe[1][63:0] -* qe[3] metadata = sse_qe[1][127:64] -*/ -_mm_storel_epi64 ((__m128i *)&qe[0 ].u.opaque_data, sse_qe[0 ]); -_mm_storeh_pd ((double *)&qe[1 ].u.opaque_data, - (__m128d )sse_qe[0 ]); -_mm_storel_epi64 ((__m128i *)&qe[2 ].u.opaque_data, sse_qe[1 ]); -_mm_storeh_pd ((double *)&qe[3 ].u.opaque_data, - (__m128d )sse_qe[1 ]); - - qe[0 ].data = ev[0 ].u64; - qe[1 ].data = ev[1 ].u64; - qe[2 ].data = ev[2 ].u64; - qe[3 ].data = ev[3 ].u64; - -break ; -case 3 : -case 2 : -case 1 : -for (i =0 ; i < num; i++) { - qe[i].cmd_byte = - cmd_byte_map[qm_port->is_directed][ev[i].op]; - qe[i].sched_type = sched_type[i]; - qe[i].data = ev[i].u64; - qe[i].qid = queue_id[i]; - qe[i].priority =EV_TO_DLB2_PRIO (ev[i].priority); - qe[i].lock_id = ev[i].flow_id; -if (sched_type[i] ==DLB2_SCHED_DIRECTED ) { -struct dlb2_msg_info *info = - (struct dlb2_msg_info *)&qe[i].lock_id; - - info->qid = queue_id[i]; - info->sched_type =DLB2_SCHED_DIRECTED ; - info->priority = qe[i].priority; - } - qe[i].u.event_type.major = ev[i].event_type; - qe[i].u.event_type.sub = ev[i].sub_event_type; - } -break ; -case 0 : -break ; - } -} - static inline int dlb2_event_enqueue_prep(struct dlb2_eventdev_port *ev_port, struct dlb2_port *qm_port,
drivers/event/dlb2/dlb2_avx512.c new file +267 -0
267 lines not on this page · raw message
drivers/event/dlb2/dlb2_priv.h +10 -0
@@ -377,6 +377,9 @@ struct dlb2_port {struct dlb2_eventdev_port *ev_port;/* back ptr */ bool use_scalar;/* force usage of scalar code */ uint16_t hw_credit_quanta; +#ifdef CC_AVX512_SUPPORT +bool use_avx512; +#endif };/* Per-process per-port mmio and memory pointers */
@@ -686,6 +689,13 @@ int dlb2_parse_params(const char *params,struct dlb2_devargs *dlb2_args, uint8_t version); +void dlb2_event_build_hcws (struct dlb2_port *qm_port, +const struct rte_event ev[], +int num, +uint8_t *sched_type, +uint8_t *queue_id); + +/* Extern globals */ extern struct process_local_port_data dlb2_port[][DLB2_NUM_PORT_TYPES ];
drivers/event/dlb2/dlb2_sve.c new file +219 -0
219 lines not on this page · raw message
drivers/event/dlb2/meson.build +53 -0
59 lines not on this page · raw message
Signature · 1 line
2.25.1
Quoted 9 lines · Timothy McDaniel
On Xeon, 512b accesses are available, so movdir64 instruction is able to perform 512b read and write to DLB producer port. In order for movdir64 to be able to pull its data from store buffers (store-buffer-forwarding) (before actual write), data should be in single 512b write format. This commit add change when code is built for Xeon with 512b AVX support to make single 512b write of all 4 QEs instead of 4x64b writes.
Signed-off-by Timothy McDaniel <[email protected]>Acked-by Kent Wires <[email protected]>
Quoted 8 lines
===
Changes since V4:
1) Add build-time control for avx512 support to meson.buildi, based on implementation found inlib/acl/meson.build
2) Addrte_vect_get_max_simd_bitwidthruntime check before using avx512 instructions
Thanks, these changes look better for runtime support. Some further more minor comments inline below.
/Bruce
Quoted 23 lines
Changes since V3:
1) Renameddlb2_noavx512.ctodlb2_sve.c, and fixed up meson.build for new file name.Changes since V1:
1) Split outdlb2_event_build_hcwsinto two implementations, one that uses AVX512 instructions, and one that does not. Each implementation is in its own source file in order to avoid build errors if the compiler does not support the newer AVX512 instructions.
2) Update meson.build to and pull in appropriate source file based on whether the compiler supports AVX512VL
3) Check if target supports AVX512VL, and use appropriate implementation based on this runtime check.--- drivers/event/dlb2/dlb2.c | 208 +----------------------- drivers/event/dlb2/dlb2_avx512.c | 267 +++++++++++++++++++++++++++++++ drivers/event/dlb2/dlb2_priv.h | 10 ++ drivers/event/dlb2/dlb2_sve.c | 219 +++++++++++++++++++++++++ drivers/event/dlb2/meson.build | 53 ++++++ 5 files changed, 556 insertions(+), 201 deletions(-) create mode 100644 drivers/event/dlb2/dlb2_avx512.c create mode 100644 drivers/event/dlb2/dlb2_sve.c
<snip>
Quoted 18 lines
drivers/event/dlb2/meson.build +10
-0@@ -19,6 +19,59 @@ sources = files( 'dlb2_selftest.c', ) +# compile AVX512 version if: +# we are building 64-bit binary (checked above) AND binutils +# can generate proper code + +if binutils_ok + + # compile AVX512 version if either: + # a. we have AVX512 supported in minimum instruction set + # baseline + # b. it's not minimum instruction set, but supported by
drivers/event/dlb2/meson.build sources = files( · line 41
Quoted 10 lines
drivers/event/dlb2/meson.build +10
-0+ # compiler + # + # in former case, just add avx512 C file to files list + # in latter case, compile c file to static lib, using correct + # compiler flags, and then have the .o file from static lib + # linked into main lib. + + # check if all required flags already enabled (variant a). + dlb2_avx512_flags = ['__AVX512F__', '__AVX512VL__', + '__AVX512CD__', '__AVX512BW__']
Minor nit: are all 4 of these really necessary? I see the runtime portion only seems to check for VL?
Quoted 21 lines
drivers/event/dlb2/meson.build +21
-0+ + dlb2_avx512_on = true + foreach f:dlb2_avx512_flags + + if cc.get_define(f, args: machine_args) == '' + dlb2_avx512_on = false + endif + endforeach + + if dlb2_avx512_on == true + + sources += files('dlb2_avx512.c') + cflags += '-DCC_AVX512_SUPPORT' + + elif cc.has_multi_arguments('-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw') + + cflags += '-DCC_AVX512_SUPPORT' + avx512_tmplib = static_library('avx512_tmp', + 'dlb2_avx512.c', + dependencies: [static_rte_eal,
drivers/event/dlb2/meson.build sources = files( · line 72
Quoted 10 lines
drivers/event/dlb2/meson.build +10
-0+ static_rte_eventdev], + c_args: cflags + + ['-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw']) + objs += avx512_tmplib.extract_objects('dlb2_avx512.c') + else + sources += files('dlb2_sve.c') + endif +else + sources += files('dlb2_sve.c')
Since this is x86 only, do you mean SSE rather than SVE?
Also, rather than adding this in the "else" legs, does the SSE version not need to always be compiled in? If the build takes the second leg, i.e. build is not mandating AVX-512, but supports it if not available, is the SSE code path not necessary for the case where the runtime machine does not support AVX-512?
Quoted 7 lines
drivers/event/dlb2/meson.build +2
-0+endif + headers = files('rte_pmd_dlb2.h') deps += ['mbuf', 'mempool', 'ring', 'pci', 'bus_pci']Signature · 1 line
2.25.1
Quoted 82 lines
-----Original Message-----
From: Richardson, Bruce <[email protected]>
Sent: Friday, June 10, 2022 8:12 AM
To: McDaniel, Timothy <[email protected]>
Cc: [email protected]; [email protected]; Wires, Kent <[email protected]>
Subject: Re: [PATCH v5] event/dlb2: add support for single 512B write of 4 QEsQuoted 9 lines · Timothy McDaniel
On Xeon, 512b accesses are available, so movdir64 instruction is able to perform 512b read and write to DLB producer port. In order for movdir64 to be able to pull its data from store buffers (store-buffer-forwarding) (before actual write), data should be in single 512b write format. This commit add change when code is built for Xeon with 512b AVX support to make single 512b write of all 4 QEs instead of 4x64b writes.
Signed-off-by Timothy McDaniel <[email protected]>Acked-by Kent Wires <[email protected]>Quoted 8 lines
===
Changes since V4:
1) Add build-time control for avx512 support to meson.buildi, based on implementation found inlib/acl/meson.build
2) Addrte_vect_get_max_simd_bitwidthruntime check before using avx512 instructionsThanks, these changes look better for runtime support. Some further more minor comments inline below.
/Bruce
Quoted 13 lines
Changes since V3:
1) Renameddlb2_noavx512.ctodlb2_sve.c, and fixed up meson.build for new file name.Changes since V1:
1) Split outdlb2_event_build_hcwsinto two implementations, one that uses AVX512 instructions, and one that does not. Each implementation is in its own source file in order to avoid build errors if the compiler does not support the newer AVX512 instructions.
2) Update meson.build to and pull in appropriate source file based on whether the compiler supports AVX512VL
3) Check if target supports AVX512VL, and use appropriate implementation based on this runtime check.Quoted 3 lines
--- drivers/event/dlb2/dlb2.c | 208 +----------------------- drivers/event/dlb2/dlb2_avx512.c | 267+++++++++++++++++++++++++++++++
Quoted 7 lines
drivers/event/dlb2/dlb2_priv.h | 10 ++ drivers/event/dlb2/dlb2_sve.c | 219 +++++++++++++++++++++++++ drivers/event/dlb2/meson.build | 53 ++++++ 5 files changed, 556 insertions(+), 201 deletions(-) create mode 100644 drivers/event/dlb2/dlb2_avx512.c create mode 100644 drivers/event/dlb2/dlb2_sve.c<snip>
Quoted 23 lines
drivers/event/dlb2/meson.build +15
-0@@ -19,6 +19,59 @@ sources = files( 'dlb2_selftest.c', ) +# compile AVX512 version if: +# we are building 64-bit binary (checked above) AND binutils +# can generate proper code + +if binutils_ok + + # compile AVX512 version if either: + # a. we have AVX512 supported in minimum instruction set + # baseline + # b. it's not minimum instruction set, but supported by + # compiler + # + # in former case, just add avx512 C file to files list + # in latter case, compile c file to static lib, using correct + # compiler flags, and then have the .o file from static lib
Quoted 9 lines
drivers/event/dlb2/meson.build sources = files( · line 41
Quoted 5 lines
drivers/event/dlb2/meson.build +5
-0+ # linked into main lib. + + # check if all required flags already enabled (variant a). + dlb2_avx512_flags = ['__AVX512F__', '__AVX512VL__', + '__AVX512CD__', '__AVX512BW__']Minor nit: are all 4 of these really necessary? I see the runtime portion only seems to check for VL?
I will update to check for just VL
Quoted 34 lines
Quoted 21 lines
drivers/event/dlb2/meson.build +21
-0+ + dlb2_avx512_on = true + foreach f:dlb2_avx512_flags + + if cc.get_define(f, args: machine_args) == '' + dlb2_avx512_on = false + endif + endforeach + + if dlb2_avx512_on == true + + sources += files('dlb2_avx512.c') + cflags += '-DCC_AVX512_SUPPORT' + + elif cc.has_multi_arguments('-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw') + + cflags += '-DCC_AVX512_SUPPORT' + avx512_tmplib = static_library('avx512_tmp', + 'dlb2_avx512.c', + dependencies: [static_rte_eal,drivers/event/dlb2/meson.build sources = files( · line 72
Quoted 10 lines
drivers/event/dlb2/meson.build +10
-0+ static_rte_eventdev], + c_args: cflags + + ['-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw']) + objs += avx512_tmplib.extract_objects('dlb2_avx512.c') + else + sources += files('dlb2_sve.c') + endif +else + sources += files('dlb2_sve.c')Since this is x86 only, do you mean SSE rather than SVE?
Quoted 6 lines
Also, rather than adding this in the "else" legs, does the SSE version not need to always be compiled in? If the build takes the second leg, i.e. build is not mandating AVX-512, but supports it if not available, is the SSE code path not necessary for the case where the runtime machine does not support AVX-512?
I'll update the name, but it's an "either or" situation. They cannot both be built as currently coded.
Quoted 7 lines
Quoted 7 lines
drivers/event/dlb2/meson.build +2
-1+endif + headers = files('rte_pmd_dlb2.h') deps += ['mbuf', 'mempool', 'ring', 'pci', 'bus_pci'] --2.25.1
Quoted 135 lines · Timothy
Quoted 82 lines
-----Original Message-----
From: Richardson, Bruce <[email protected]>
Sent: Friday, June 10, 2022 8:12 AM
To: McDaniel, Timothy <[email protected]>
Cc: [email protected]; [email protected]; Wires, Kent <[email protected]>
Subject: Re: [PATCH v5] event/dlb2: add support for single 512B write of 4 QEsQuoted 9 lines · Timothy McDaniel
On Xeon, 512b accesses are available, so movdir64 instruction is able to perform 512b read and write to DLB producer port. In order for movdir64 to be able to pull its data from store buffers (store-buffer-forwarding) (before actual write), data should be in single 512b write format. This commit add change when code is built for Xeon with 512b AVX support to make single 512b write of all 4 QEs instead of 4x64b writes.
Signed-off-by Timothy McDaniel <[email protected]>Acked-by Kent Wires <[email protected]>Quoted 8 lines
===
Changes since V4:
1) Add build-time control for avx512 support to meson.buildi, based on implementation found inlib/acl/meson.build
2) Addrte_vect_get_max_simd_bitwidthruntime check before using avx512 instructionsThanks, these changes look better for runtime support. Some further more minor comments inline below.
/Bruce
Quoted 13 lines
Changes since V3:
1) Renameddlb2_noavx512.ctodlb2_sve.c, and fixed up meson.build for new file name.Changes since V1:
1) Split outdlb2_event_build_hcwsinto two implementations, one that uses AVX512 instructions, and one that does not. Each implementation is in its own source file in order to avoid build errors if the compiler does not support the newer AVX512 instructions.
2) Update meson.build to and pull in appropriate source file based on whether the compiler supports AVX512VL
3) Check if target supports AVX512VL, and use appropriate implementation based on this runtime check.Quoted 3 lines
--- drivers/event/dlb2/dlb2.c | 208 +----------------------- drivers/event/dlb2/dlb2_avx512.c | 267+++++++++++++++++++++++++++++++
Quoted 7 lines
drivers/event/dlb2/dlb2_priv.h | 10 ++ drivers/event/dlb2/dlb2_sve.c | 219 +++++++++++++++++++++++++ drivers/event/dlb2/meson.build | 53 ++++++ 5 files changed, 556 insertions(+), 201 deletions(-) create mode 100644 drivers/event/dlb2/dlb2_avx512.c create mode 100644 drivers/event/dlb2/dlb2_sve.c<snip>
Quoted 23 lines
drivers/event/dlb2/meson.build +15
-0@@ -19,6 +19,59 @@ sources = files( 'dlb2_selftest.c', ) +# compile AVX512 version if: +# we are building 64-bit binary (checked above) AND binutils +# can generate proper code + +if binutils_ok + + # compile AVX512 version if either: + # a. we have AVX512 supported in minimum instruction set + # baseline + # b. it's not minimum instruction set, but supported by + # compiler + # + # in former case, just add avx512 C file to files list + # in latter case, compile c file to static lib, using correct + # compiler flags, and then have the .o file from static libQuoted 9 lines
drivers/event/dlb2/meson.build sources = files( · line 41
Quoted 5 lines
drivers/event/dlb2/meson.build +5
-0+ # linked into main lib. + + # check if all required flags already enabled (variant a). + dlb2_avx512_flags = ['__AVX512F__', '__AVX512VL__', + '__AVX512CD__', '__AVX512BW__']Minor nit: are all 4 of these really necessary? I see the runtime portion only seems to check for VL?
I will update to check for just VL
Quoted 34 lines
Quoted 21 lines
drivers/event/dlb2/meson.build +21
-0+ + dlb2_avx512_on = true + foreach f:dlb2_avx512_flags + + if cc.get_define(f, args: machine_args) == '' + dlb2_avx512_on = false + endif + endforeach + + if dlb2_avx512_on == true + + sources += files('dlb2_avx512.c') + cflags += '-DCC_AVX512_SUPPORT' + + elif cc.has_multi_arguments('-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw') + + cflags += '-DCC_AVX512_SUPPORT' + avx512_tmplib = static_library('avx512_tmp', + 'dlb2_avx512.c', + dependencies: [static_rte_eal,drivers/event/dlb2/meson.build sources = files( · line 72
Quoted 10 lines
drivers/event/dlb2/meson.build +10
-0+ static_rte_eventdev], + c_args: cflags + + ['-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw']) + objs += avx512_tmplib.extract_objects('dlb2_avx512.c') + else + sources += files('dlb2_sve.c') + endif +else + sources += files('dlb2_sve.c')Since this is x86 only, do you mean SSE rather than SVE?
Quoted 6 lines
Also, rather than adding this in the "else" legs, does the SSE version not need to always be compiled in? If the build takes the second leg, i.e. build is not mandating AVX-512, but supports it if not available, is the SSE code path not necessary for the case where the runtime machine does not support AVX-512?
Quoted 3 lines
I'll update the name, but it's an "either or" situation. They cannot both be built as currently coded.
If only the AVX-512 path is built, what happens when the runtime check for AVX-512 fails? Is there a scalar path that is used as fallback?
/Bruce
Quoted 148 lines
-----Original Message-----
From: Richardson, Bruce <[email protected]>
Sent: Friday, June 10, 2022 10:43 AM
To: McDaniel, Timothy <[email protected]>
Cc: [email protected]; [email protected]; Wires, Kent <[email protected]>
Subject: Re: [PATCH v5] event/dlb2: add support for single 512B write of 4 QEsQuoted 8 lines · Timothy
Quoted 8 lines
-----Original Message-----
From: Richardson, Bruce <[email protected]>
Sent: Friday, June 10, 2022 8:12 AM
To: McDaniel, Timothy <[email protected]>
Cc: [email protected]; [email protected]; Wires, Kent <[email protected]>
Subject: Re: [PATCH v5] event/dlb2: add support for single 512B write of 4QEs
Quoted 49 lines
Quoted 49 lines · Timothy McDaniel
Quoted 9 lines
On Xeon, 512b accesses are available, so movdir64 instruction is able to perform 512b read and write to DLB producer port. In order for movdir64 to be able to pull its data from store buffers (store-buffer-forwarding) (before actual write), data should be in single 512b write format. This commit add change when code is built for Xeon with 512b AVX support to make single 512b write of all 4 QEs instead of 4x64b writes.
Signed-off-by Timothy McDaniel <[email protected]>Acked-by Kent Wires <[email protected]>Quoted 8 lines
===
Changes since V4:
1) Add build-time control for avx512 support to meson.buildi, based on implementation found inlib/acl/meson.build
2) Addrte_vect_get_max_simd_bitwidthruntime check before using avx512 instructionsThanks, these changes look better for runtime support. Some further more minor comments inline below.
/Bruce
Quoted 13 lines
Changes since V3:
1) Renameddlb2_noavx512.ctodlb2_sve.c, and fixed up meson.build for new file name.Changes since V1:
1) Split outdlb2_event_build_hcwsinto two implementations, one that uses AVX512 instructions, and one that does not. Each implementation is in its own source file in order to avoid build errors if the compiler does not support the newer AVX512 instructions.
2) Update meson.build to and pull in appropriate source file based on whether the compiler supports AVX512VL
3) Check if target supports AVX512VL, and use appropriate implementation based on this runtime check.Quoted 3 lines
--- drivers/event/dlb2/dlb2.c | 208 +----------------------- drivers/event/dlb2/dlb2_avx512.c | 267+++++++++++++++++++++++++++++++
Quoted 7 lines
drivers/event/dlb2/dlb2_priv.h | 10 ++ drivers/event/dlb2/dlb2_sve.c | 219 +++++++++++++++++++++++++ drivers/event/dlb2/meson.build | 53 ++++++ 5 files changed, 556 insertions(+), 201 deletions(-) create mode 100644 drivers/event/dlb2/dlb2_avx512.c create mode 100644 drivers/event/dlb2/dlb2_sve.cQuoted 3 lines
Quoted 3 lines
<snip>
Review
Quoted 1 line
(quoted diff) +0
-0b/drivers/event/dlb2/meson.build
Quoted 32 lines
Quoted 22 lines
Quoted 22 lines
index
f963589fd3..58146e8aef100644drivers/event/dlb2/meson.build +15
-0@@ -19,6 +19,59 @@ sources = files( 'dlb2_selftest.c', ) +# compile AVX512 version if: +# we are building 64-bit binary (checked above) AND binutils +# can generate proper code + +if binutils_ok + + # compile AVX512 version if either: + # a. we have AVX512 supported in minimum instruction set + # baseline + # b. it's not minimum instruction set, but supported by + # compiler + # + # in former case, just add avx512 C file to files list + # in latter case, compile c file to static lib, using correct + # compiler flags, and then have the .o file from static libQuoted 9 lines
drivers/event/dlb2/meson.build sources = files( · line 41
Quoted 5 lines
drivers/event/dlb2/meson.build +5
-0+ # linked into main lib. + + # check if all required flags already enabled (variant a). + dlb2_avx512_flags = ['__AVX512F__', '__AVX512VL__', + '__AVX512CD__', '__AVX512BW__']Minor nit: are all 4 of these really necessary? I see the runtime portion only seems to check for VL?
Quoted 40 lines
I will update to check for just VL
Quoted 38 lines
Quoted 21 lines
drivers/event/dlb2/meson.build +21
-0+ + dlb2_avx512_on = true + foreach f:dlb2_avx512_flags + + if cc.get_define(f, args: machine_args) == '' + dlb2_avx512_on = false + endif + endforeach + + if dlb2_avx512_on == true + + sources += files('dlb2_avx512.c') + cflags += '-DCC_AVX512_SUPPORT' + + elif cc.has_multi_arguments('-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw') + + cflags += '-DCC_AVX512_SUPPORT' + avx512_tmplib = static_library('avx512_tmp', + 'dlb2_avx512.c', + dependencies: [static_rte_eal,drivers/event/dlb2/meson.build sources = files( · line 72
Quoted 10 lines
drivers/event/dlb2/meson.build +10
-0+ static_rte_eventdev], + c_args: cflags + + ['-mavx512f', '-mavx512vl', + '-mavx512cd', '-mavx512bw']) + objs += avx512_tmplib.extract_objects('dlb2_avx512.c') + else + sources += files('dlb2_sve.c') + endif +else + sources += files('dlb2_sve.c')Since this is x86 only, do you mean SSE rather than SVE?
Also, rather than adding this in the "else" legs, does the SSE version not need to always be compiled in? If the build takes the second leg, i.e. build is not mandating AVX-512, but supports it if not available, is the SSE code path not necessary for the case where the runtime machine does
not
Quoted 3 lines
Quoted 2 lines
support AVX-512?
Quoted 7 lines
Quoted 3 lines
I'll update the name, but it's an "either or" situation. They cannot both be built as currently coded.
If only the AVX-512 path is built, what happens when the runtime check for AVX-512 fails? Is there a scalar path that is used as fallback?
/Bruce
The file dlb2_avx512.c contains a runtime check that controls whether avx512 instructions are used. That file contains both implementations. The dlb2_sse.c file contains only the original/sse implementation.
Thanks,
Tim