From: "Zhu, Heqing" <heqing.zhu@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhu, Heqing" <heqing.zhu@intel.com>
Subject: [dpdk-dev] Hyperscan Boot Camp 2018 on Nov 9th Friday, Santa Clara.
Date: Tue, 6 Nov 2018 16:53:32 +0000 [thread overview]
Message-ID: <CAD16F236028A64DBBC0158B1636EA45678BEFEC@fmsmsx124.amr.corp.intel.com> (raw)
We still have a few seats available for the first Hyperscan boot camp training day at Intel office, Santa Clara on Nov 9th 2018. If you are interested to join us, please come to this website and complete the registration<https://www.surveymonkey.com/r/V2LRN3R>. Below please find the initial agenda. If your request is not accommodated this time, still 5 seats available, we will look at the next event opportunity.
And we do talk about a combined use case with DPDK, so this is somewhat relevant. Registration website: http://www.Hyperscan.io
The current event agenda.
Hyperscan 101 (Features and APIs) by Ravisundar Subhiksha, Xiang Wang, 9:150~11:15
What's Hyperscan, Regular Expression?
Why and when will use Hyperscan?
Hands-on Lab compiling and run Hyperscan on Linux
The APIs and basic working mode
How to migrate from PCRE to Hyperscan
Hyperscan 202 (Tools and utilities, performance benchmark and tunings) by Xiang Wang, 11:15 ~ 12:15
hscheck, hscollider, hsdump
hsbench and the performance optimization tips
Lunch and Social Break
Intel(r) Resource Director Technology by Autee Priya, 13:00~13:45
Cache Monitor and Allocation, Memory bandwidth and Allocation technology
Hyperscan/Hsbench experiment with Intel RDT
Q&A
Hyperscan 303 (Use case with DPI, Snort) by Xiang Wang, 14:00~15:30
Case Study: nDPI and Hyperscan.
Case study: Snort/DPDK/Container
Open Discussion (15:40~16:30)
Industrial pattern matching benchmark
Hyperscan feedback, new features, use case
Future works
Pre-work:
Please bring your development environment to follow up the on class steps. Please download the source code on www.Hyperscan.io<http://www.Hyperscan.io>. Hopefully, we will try to provide the Internet access at the workshop, it is subject to change.
Linux OS (VM Guest is fine)
Ubuntu 16.04 LTS or newer
CentOS 7 or newer
Software tools:
Cmake >=2.8.11
Ragel 6.9
Python 2.7
Boost >= 1.57
PCAP >=0.8
Sqite3 >3.22
reply other threads:[~2018-11-06 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAD16F236028A64DBBC0158B1636EA45678BEFEC@fmsmsx124.amr.corp.intel.com \
--to=heqing.zhu@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).