From: "Varghese, Vipin" <Vipin.Varghese@amd.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] doc/dmadevs: add note clarifying naming of idxd devices
Date: Wed, 26 Jul 2023 00:51:56 +0000 [thread overview]
Message-ID: <MN2PR12MB3085992FB4FB053F2B3050278200A@MN2PR12MB3085.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ZL/167K4w5xAyVHW@bricha3-MOBL.ger.corp.intel.com>
[AMD Official Use Only - General]
> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: Tuesday, July 25, 2023 9:49 PM
> To: dev@dpdk.org
> Cc: Varghese, Vipin <Vipin.Varghese@amd.com>
> Subject: Re: [PATCH] doc/dmadevs: add note clarifying naming of idxd devices
>
> Caution: This message originated from an External Source. Use proper
> caution when opening attachments, clicking links, or responding.
>
>
> On Tue, Jul 25, 2023 at 05:16:29PM +0100, Bruce Richardson wrote:
> > Since the test-dma-perf application identifies devices by name,
> > include in the idxd driver documentation a note on device naming when
> vfio-pci.
> > See also discussion in bugzilla[1].
> >
> > [1] https://bugs.dpdk.org/show_bug.cgi?id=1268
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
> Note, although I reference bugzilla here, I don't consider this a bugfix, so I've
> not included a fixes tag and official bugzilla id etc. It's instead a note clarifying
> the expected behaviour.
App/dma-perf got integrated into DPDK via `https://patches.dpdk.org/project/dpdk/patch/20230629131455.52732-1-cheng1.jiang@intel.com/`. The expectation is that, it is tried and tested for hardware dma, sw skeleton dma and cpu memcpy.
Happy to acknowledge the change as it helps the DPDK community.
Acked-by: Vipin Varghese <vipin.varghese@amd.com>
>
> /Bruce
next prev parent reply other threads:[~2023-07-26 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 16:16 Bruce Richardson
2023-07-25 16:18 ` Bruce Richardson
2023-07-26 0:51 ` Varghese, Vipin [this message]
2023-07-27 21:55 ` Thomas Monjalon
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=MN2PR12MB3085992FB4FB053F2B3050278200A@MN2PR12MB3085.namprd12.prod.outlook.com \
--to=vipin.varghese@amd.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).