From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 0/3] Regexp speedup
Date: Thu, 22 Apr 2010 15:29:01 +0200 [thread overview]
Message-ID: <cover.1271942633.git.zkabelac@redhat.com> (raw)
This patch set uses latest EJT code.
2 first patches reverts current regexp optimization code away.
3rd patch adds improved way of calculating dfa states
Patch is not so well tested - but some elementar cases seems to be passing.
Signed-off-by: Zdenek Kabelac <zkabelac@redhat.com>
Zdenek Kabelac (3):
Revert "Still not satisfactory..."
Revert "Add a regex optimisation pass for shared character prefixes."
New regexp code made by EJT.
WHATS_NEW_DM | 1 -
libdm/regex/matcher.c | 265 +++++++++++++++++++++++++++---------------------
libdm/regex/parse_rx.c | 215 ++-------------------------------------
libdm/regex/parse_rx.h | 1 +
4 files changed, 159 insertions(+), 323 deletions(-)
next reply other threads:[~2010-04-22 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:29 Zdenek Kabelac [this message]
2010-04-22 13:29 ` [PATCH 1/3] Revert "Still not satisfactory..." Zdenek Kabelac
2010-04-22 13:29 ` [PATCH 2/3] Revert "Add a regex optimisation pass for shared character prefixes." Zdenek Kabelac
2010-04-22 13:29 ` [PATCH 3/3] New regexp code made by EJT Zdenek Kabelac
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=cover.1271942633.git.zkabelac@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.