[Oisf-devel] [COMMIT] OISF branch, master, updated. suricata-1.3.1-2-g452d3c4

noreply at openinfosecfoundation.org noreply at openinfosecfoundation.org
Wed Aug 22 07:05:54 UTC 2012

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "OISF".

The branch, master has been updated
       via  452d3c43089526c2859ac6da54718bf0b2294480 (commit)
       via  f389a1201f910aa7c614c51e9af8cebcd187236a (commit)
      from  e28835af9199d868212c2de5b04b5c1fdc9b3372 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 452d3c43089526c2859ac6da54718bf0b2294480
Author: Eric Leblond <eric at regit.org>
Date:   Thu Aug 9 16:47:52 2012 +0200

    tm-thread: exit loop if suri want to quit

commit f389a1201f910aa7c614c51e9af8cebcd187236a
Author: Eric Leblond <eric at regit.org>
Date:   Thu Aug 9 16:24:18 2012 +0200

    tm-thread: run thread init function sequentially.
    On some setup you want to run each thread init function sequentially.
    For example, if I use flow_cpu load balancing on AF_PACKET, my target
    is to have CPU 0 (first socket in the group) to be link with the
    thread 0 in detect cpu set (first thread to be initialised). A good
    way to achieve this is to run only one thread init function at a time
    to avoid any possible race condition.


Summary of changes:
 src/tm-threads.c |    5 ++++-
 1 files changed, 4 insertions(+), 1 deletions(-)


More information about the Oisf-devel mailing list