DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] raw/common: introduce the Multi-function API
Date: Thu, 2 Apr 2020 09:46:46 +0000	[thread overview]
Message-ID: <MN2PR11MB37252330456F0A8A9BBB196E9CC60@MN2PR11MB3725.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1967048.aiPYRZItUj@xps>

Hi,

The purpose of the Multi-function API is to enable a broader set of transforms that aren't compression /crypto specific (CRC for example)
We had quite a few discussions on Multi-function in the mails below 

http://mails.dpdk.org/archives/dev/2020-February/157045.html
http://mails.dpdk.org/archives/dev/2020-March/159189.html

The v2 patchset will be ready for this in the coming days and we will include a cover-letter describing the feature and referencing back to the RFC discussion this time around

Regards,
Mairtin

-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net> 
Sent: Wednesday, April 1, 2020 10:31 PM
To: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] raw/common: introduce the Multi-function API

Hi,

16/03/2020 20:21, Mairtin o Loingsigh:
> Multi-function API allows user to chain xforms of various types 
> together in a single operation

Please could you elaborate a bit more?
Which problem are you trying to address?
What is the design?
How it can be used?

For such feature proposal, I recommend a design discussion before starting the development.



  reply	other threads:[~2020-04-02  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 19:21 Mairtin o Loingsigh
2020-04-01 21:31 ` Thomas Monjalon
2020-04-02  9:46   ` O'loingsigh, Mairtin [this message]
2020-04-02 13:00     ` 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=MN2PR11MB37252330456F0A8A9BBB196E9CC60@MN2PR11MB3725.namprd11.prod.outlook.com \
    --to=mairtin.oloingsigh@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).