DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Pai G, Sunil" <sunil.pai.g@intel.com>
To: "Laatz, Kevin" <kevin.laatz@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"Laatz, Kevin" <kevin.laatz@intel.com>
Subject: RE: [PATCH v3] dma/idxd: add generic option for queue config
Date: Mon, 4 Apr 2022 09:58:33 +0000	[thread overview]
Message-ID: <DM8PR11MB5605D76DA5A366FCF0278F7BBDE59@DM8PR11MB5605.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220401103500.697597-1-kevin.laatz@intel.com>


> -----Original Message-----
> From: Kevin Laatz <kevin.laatz@intel.com>
> Sent: Friday, April 1, 2022 4:05 PM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; Laatz, Kevin
> <kevin.laatz@intel.com>
> Subject: [PATCH v3] dma/idxd: add generic option for queue config
> 
> The device config script currently uses some defaults to configure devices
> in a generic way.
> 
> With the addition of this option, users have more control over how queues
> are configured.
> 
> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
> ---
>  drivers/dma/idxd/dpdk_idxd_cfg.py | 34 +++++++++++++++++++++----------
>  1 file changed, 23 insertions(+), 11 deletions(-)
> 

Tried setting few capabilities of a dedicated WQ, works as expected.

Tested-by: Sunil Pai G <sunil.pai.g@intel.com>



      parent reply	other threads:[~2022-04-04  9:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-30 15:07 [PATCH] " Kevin Laatz
2022-03-31 14:57 ` Bruce Richardson
2022-03-31 15:47   ` Kevin Laatz
2022-03-31 17:21 ` [PATCH v2] " Kevin Laatz
2022-04-01  9:08   ` Bruce Richardson
2022-04-01 10:35   ` [PATCH v3] " Kevin Laatz
2022-04-01 10:51     ` Bruce Richardson
2022-06-07 10:47       ` Thomas Monjalon
2022-04-04  9:58     ` Pai G, Sunil [this message]

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=DM8PR11MB5605D76DA5A366FCF0278F7BBDE59@DM8PR11MB5605.namprd11.prod.outlook.com \
    --to=sunil.pai.g@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@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).