[v4,0/3] DLB2 Enhancements

  This patchset  addresses DLB enhancements in the DLB driver.

Abdullah Sevincer (3):
  event/dlb2: add support for HW delayed token
  event/dlb2: add support for dynamic HL entries
  event/dlb2: enhance DLB credit handling

 app/test-eventdev/test_perf_common.c       |  20 +-
 drivers/event/dlb2/dlb2.c                  | 385 ++++++++++++++++++---
 drivers/event/dlb2/dlb2_iface.c            |   3 +
 drivers/event/dlb2/dlb2_iface.h            |   4 +-
 drivers/event/dlb2/dlb2_priv.h             |  16 +-
 drivers/event/dlb2/dlb2_user.h             |  24 ++
 drivers/event/dlb2/meson.build             |  12 +
 drivers/event/dlb2/meson_options.txt       |   6 +
 drivers/event/dlb2/pf/base/dlb2_regs.h     |   9 +
 drivers/event/dlb2/pf/base/dlb2_resource.c |  95 ++++-
 drivers/event/dlb2/pf/base/dlb2_resource.h |  19 +
 drivers/event/dlb2/pf/dlb2_pf.c            |  28 +-
 drivers/event/dlb2/rte_pmd_dlb2.c          |  29 ++
 drivers/event/dlb2/rte_pmd_dlb2.h          |  41 +++
 drivers/event/dlb2/version.map             |   3 +
 15 files changed, 630 insertions(+), 64 deletions(-)
 create mode 100644 drivers/event/dlb2/meson_options.txt
  

On Wed, May 01, 2024 at 02:46:17PM -0500, Abdullah Sevincer wrote:
> This patchset  addresses DLB enhancements in the DLB driver.
> 
> Abdullah Sevincer (3):
>   event/dlb2: add support for HW delayed token
>   event/dlb2: add support for dynamic HL entries
>   event/dlb2: enhance DLB credit handling
> 
Hi Abdullah,

Couple of small asks/tips when sending new versions of a patchset:
1) When sending v2, v3, v4 using git-send-email, include
  "--in-reply-to <message-id-of-v1-cover-letter>" in the command. This will
  ensure all copies of the patches get put in the same email thread, rather
  than having different versions spread throughout the reader's mailbox.
2) Please include in the cover letter a short one/two-line description of
  what has changed in each version, so anyone reviewing e.g. v4 after
  reading v3, is aware of what parts of v4 they need to look at
  specifically. Generally, this should be in reverse order e.g.

v4: renamed bar to foobar
v3: changed foo to bar
v2: added new foo

Thanks,
/Bruce
  

>+Hi Abdullah,

>+Couple of small asks/tips when sending new versions of a patchset:
>+1) When sending v2, v3, v4 using git-send-email, include
 >+ "--in-reply-to <message-id-of-v1-cover-letter>" in the command. This will
 >+ ensure all copies of the patches get put in the same email thread, rather
  >+than having different versions spread throughout the reader's mailbox.
>+2) Please include in the cover letter a short one/two-line description of
 >+ what has changed in each version, so anyone reviewing e.g. v4 after
  >+reading v3, is aware of what parts of v4 they need to look at
 >+ specifically. Generally, this should be in reverse order e.g.

>+v4: renamed bar to foobar
>+v3: changed foo to bar
>+v2: added new foo

>+Thanks,
>+/Bruce

Hi Bruce,

Thanks for the tips, and sorry for filling in the inboxes, I will follow your instructions 
for the following patches.