DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ori Kam <orika@mellanox.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
	Wang Xiang <xiang.w.wang@intel.com>,
	 Guy Kaneti <guyk@marvell.com>, dpdk-dev <dev@dpdk.org>,
	 Pavan Nikhilesh <pbhagavatula@marvell.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	 Hemant Agrawal <hemant.agrawal@nxp.com>,
	Opher Reviv <opher@mellanox.com>,
	 Alex Rosenbaum <alexr@mellanox.com>,
	Dovrat Zifroni <dovrat@marvell.com>,
	 Prasun Kapoor <pkapoor@marvell.com>,
	Nipun Gupta <nipun.gupta@nxp.com>,
	 "Richardson, Bruce" <bruce.richardson@intel.com>,
	yang.a.hong@intel.com, harry.chang@intel.com,
	 gu.jian1@zte.com.cn, shanjiangh@chinatelecom.cn,
	zhangy.yun@chinatelecom.cn,  lixingfu@huachentel.com,
	wushuai@inspur.com, yuyingxia@yxlink.com,
	 fanchenggang@sunyainfo.com, davidfgao@tencent.com,
	liuzhong1@chinaunicom.cn,  zhaoyong11@huawei.com, oc@yunify.com,
	Jim Thompson <jim@netgate.com>,
	 hongjun.ni@intel.com, j.bromhead@titan-ic.com, deri@ntop.org,
	fc@napatech.com,  arthur.su@lionic.com,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [RFC] app/test-regex: add RegEx test application.
Date: Thu, 4 Jun 2020 10:26:20 +0530	[thread overview]
Message-ID: <CALBAE1OyKaptSt5AUaVtERDVcTJWOX=os=UFj=5F9E1VPKCWDw@mail.gmail.com> (raw)
In-Reply-To: <1591219752-46544-1-git-send-email-orika@mellanox.com>

On Thu, Jun 4, 2020 at 2:59 AM Ori Kam <orika@mellanox.com> wrote:
>
> Following the new RegEx class [1].
> There is a need to create a dedecated test application in order to
> validate this class and PMD.
>
> Unlike net device this application loads data from a file.
>
> This commit introduce the new RegEx test app.
>
> The basic app flow:
> 1. query probed RegEx device.
> 2. configure the probed device accoding to the device caps.
> 3. read a rule database file.
> 4. read a data file to be searched.
> 5. allocate one mbuf.
> 6. select the request job len, based on the number of jobs requsted.
> 7. create one RegEx op which uses the mbuf defined in step 5.
> 8. attach the data buffer at offset 0 with len accoding to request
>    len to the mbuf as external buffer.
> 9. enqueue one job.
> 10. wait for completion of the job.
> 11. check job results and print them.
> 12. move the mbuf to point to the next part of the buffer.
> 13. while there are more parts jump to 9.
>
> Future improvments to this application may include:
> 1. submiting more then one job at a time.
> 2. working with more then one queue.
> 3. support out of order.
> 4. allow runtime rule updating.
>
> This commit is only at RFC level, which means that
> the code is only basic reference and can't be compiled and doesn't
> include error or edge case handling.
>
> [1]https://patches.dpdk.org/cover/69919/
>
> Signed-off-by: Ori Kam <orika@mellanox.com>

IMO, this kind simile application with fixed-function can go in the
example folder.
I think, for app/test-regex, it better to have a framework to add new
tests, modes, parse the modes, etc.
Please see git log app/test-eventdev/ initial check-ins for the
skeleton as a reference

  reply	other threads:[~2020-06-04  4:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 21:29 Ori Kam
2020-06-04  4:56 ` Jerin Jacob [this message]
2020-06-04  5:51   ` Ori Kam
2020-06-04  6:30     ` Jerin Jacob
2020-06-04 11:31       ` Ori Kam

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='CALBAE1OyKaptSt5AUaVtERDVcTJWOX=os=UFj=5F9E1VPKCWDw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=alexr@mellanox.com \
    --cc=arthur.su@lionic.com \
    --cc=bruce.richardson@intel.com \
    --cc=davidfgao@tencent.com \
    --cc=deri@ntop.org \
    --cc=dev@dpdk.org \
    --cc=dovrat@marvell.com \
    --cc=fanchenggang@sunyainfo.com \
    --cc=fc@napatech.com \
    --cc=gu.jian1@zte.com.cn \
    --cc=guyk@marvell.com \
    --cc=harry.chang@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=hongjun.ni@intel.com \
    --cc=j.bromhead@titan-ic.com \
    --cc=jerinj@marvell.com \
    --cc=jim@netgate.com \
    --cc=liuzhong1@chinaunicom.cn \
    --cc=lixingfu@huachentel.com \
    --cc=nipun.gupta@nxp.com \
    --cc=oc@yunify.com \
    --cc=opher@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=pbhagavatula@marvell.com \
    --cc=pkapoor@marvell.com \
    --cc=shahafs@mellanox.com \
    --cc=shanjiangh@chinatelecom.cn \
    --cc=thomas@monjalon.net \
    --cc=wushuai@inspur.com \
    --cc=xiang.w.wang@intel.com \
    --cc=yang.a.hong@intel.com \
    --cc=yuyingxia@yxlink.com \
    --cc=zhangy.yun@chinatelecom.cn \
    --cc=zhaoyong11@huawei.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).