DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Sevincer, Abdullah" <abdullah.sevincer@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Marchand, David" <david.marchand@redhat.com>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	 "Chen, Mike Ximing" <mike.ximing.chen@intel.com>,
	"Sarkar, Tirthendu" <tirthendu.sarkar@intel.com>,
	"Pathak, Pravin" <pravin.pathak@intel.com>,
	"Doneria, Shivani" <shivani.doneria@intel.com>
Subject: RE: [PATCH v5 3/5] event/dlb2: enhance DLB credit handling
Date: Wed, 26 Jun 2024 00:26:21 +0000	[thread overview]
Message-ID: <CY8PR11MB6890A64C1C678B86B30AB543E9D62@CY8PR11MB6890.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1OWoKxojDCYeeqRv8bi_oU4Sf0M3K2ba5EnkfPvztfpeQ@mail.gmail.com>


>++ @Richardson, Bruce  @Thomas Monjalon  @David Marchand @Ferruh Yigit

>+It is not allowed to add PMD specific build options in generic DPDK build options.  Please check with Bruce.

>+You may use scheme like
>+>+https://patches.dpdk.org/project/dpdk/patch/20240522192139.3016-1-pbhagavatula@marvell.com/

>+or if we think, we need to standardize the PMD compilation options, then we can do that as well.

Thanks Jerrin, I will check the scheme. I will send 2 patches(dynamic hl and hw delayed token) together(as patch set) separately from this one and address this one later if that’s ok?

  reply	other threads:[~2024-06-26  0:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 19:46 [PATCH v4 0/3] DLB2 Enhancements Abdullah Sevincer
2024-05-01 19:46 ` [PATCH v4 1/3] event/dlb2: add support for HW delayed token Abdullah Sevincer
2024-05-27 15:19   ` Jerin Jacob
2024-06-19 21:01   ` [PATCH v5 0/5] DLB2 Enhancements Abdullah Sevincer
2024-06-19 21:01     ` [PATCH v5 1/5] event/dlb2: add support for HW delayed token Abdullah Sevincer
2024-06-20 12:01       ` Jerin Jacob
2024-06-19 21:01     ` [PATCH v5 2/5] event/dlb2: add support for dynamic HL entries Abdullah Sevincer
2024-06-19 21:01     ` [PATCH v5 3/5] event/dlb2: enhance DLB credit handling Abdullah Sevincer
2024-06-20 12:09       ` Jerin Jacob
2024-06-26  0:26         ` Sevincer, Abdullah [this message]
2024-06-26  9:37           ` Jerin Jacob
2024-06-19 21:01     ` [PATCH v5 4/5] doc: update DLB2 documentation Abdullah Sevincer
2024-06-19 21:01     ` [PATCH v5 5/5] doc: update release notes for 24.07 Abdullah Sevincer
2024-06-20  7:02       ` David Marchand
2024-05-01 19:46 ` [PATCH v4 2/3] event/dlb2: add support for dynamic HL entries Abdullah Sevincer
2024-05-27 15:23   ` Jerin Jacob
2024-05-01 19:46 ` [PATCH v4 3/3] event/dlb2: enhance DLB credit handling Abdullah Sevincer
2024-05-27 15:30   ` Jerin Jacob
2024-06-04 18:22     ` Sevincer, Abdullah
2024-06-05  4:02       ` Jerin Jacob
2024-06-19 21:07         ` Sevincer, Abdullah
2024-05-02  7:34 ` [PATCH v4 0/3] DLB2 Enhancements Bruce Richardson
2024-05-02 15:52   ` Sevincer, Abdullah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CY8PR11MB6890A64C1C678B86B30AB543E9D62@CY8PR11MB6890.namprd11.prod.outlook.com \
    --to=abdullah.sevincer@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=mike.ximing.chen@intel.com \
    --cc=pravin.pathak@intel.com \
    --cc=shivani.doneria@intel.com \
    --cc=thomas@monjalon.net \
    --cc=tirthendu.sarkar@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).