[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Grep-devel] [PATCH 0/4] search backend thread safety
From: |
Jim Meyering |
Subject: |
Re: [Grep-devel] [PATCH 0/4] search backend thread safety |
Date: |
Sun, 25 Dec 2016 10:54:42 +0100 |
On Sun, Dec 25, 2016 at 9:57 AM, Zev Weiss <address@hidden> wrote:
> Hello,
>
> In another incremental step toward enabling multithreading in grep
> (and reducing the size of my out-of-tree multithreading patch set),
> this patch series removes global state from grep's various search
> backends (kwsearch, dfasearch, pcresearch) by returning an opaque
> pointer from the compile() functions and passing it back into the
> execute() functions.
Thanks for making it easy.
I've reviewed, tested and pushed those four commits.
- [Grep-devel] [PATCH 0/4] search backend thread safety, Zev Weiss, 2016/12/25
- [Grep-devel] [PATCH 1/4] grep: prepare search backends for thread-safety, Zev Weiss, 2016/12/25
- [Grep-devel] [PATCH 3/4] kwsearch: thread safety, Zev Weiss, 2016/12/25
- [Grep-devel] [PATCH 2/4] dfasearch: thread safety, Zev Weiss, 2016/12/25
- [Grep-devel] [PATCH 4/4] pcresearch: thread safety, Zev Weiss, 2016/12/25
- Re: [Grep-devel] [PATCH 0/4] search backend thread safety,
Jim Meyering <=
- Re: [Grep-devel] [PATCH 0/4] search backend thread safety, Paul Eggert, 2016/12/25