public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Suricata: drop unused cuda HW acceleration
Date: Tue, 29 Jan 2019 14:11:21 +0100	[thread overview]
Message-ID: <6916aabc790bad7d32974024520436ace5d4a627.camel@ipfire.org> (raw)
In-Reply-To: <086629c5-299f-5c85-c650-b498024aa669@link38.eu>

[-- Attachment #1: Type: text/plain, Size: 2582 bytes --]

Hello Peter,

thanks for your patch - merged!

Best regards,

-Stefan
> As stated in https://bugzilla.ipfire.org/show_bug.cgi?id=11808#c5 ,
> Cuda hardware acceleration is unused and so the configuration file
> section can be removed.
> 
> This partially addresses #11808.
> 
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> Cc: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
>  config/suricata/suricata.yaml | 35 -------------------------------
> ----
>  1 file changed, 35 deletions(-)
> 
> diff --git a/config/suricata/suricata.yaml
> b/config/suricata/suricata.yaml
> index 94e13f501..55b6c05cf 100644
> --- a/config/suricata/suricata.yaml
> +++ b/config/suricata/suricata.yaml
> @@ -933,41 +933,6 @@ profiling:
>      filename: pcaplog_stats.log
>      append: yes
>  
> -##
> -## Hardware accelaration
> -##
> -
> -# Cuda configuration.
> -cuda:
> -  # The "mpm" profile.  On not specifying any of these parameters,
> the engine's
> -  # internal default values are used, which are same as the ones
> specified in
> -  # in the default conf file.
> -  mpm:
> -    # The minimum length required to buffer data to the gpu.
> -    # Anything below this is MPM'ed on the CPU.
> -    # Can be specified in kb, mb, gb.  Just a number indicates it's
> in bytes.
> -    # A value of 0 indicates there's no limit.
> -    data-buffer-size-min-limit: 0
> -    # The maximum length for data that we would buffer to the gpu.
> -    # Anything over this is MPM'ed on the CPU.
> -    # Can be specified in kb, mb, gb.  Just a number indicates it's
> in bytes.
> -    data-buffer-size-max-limit: 1500
> -    # The ring buffer size used by the CudaBuffer API to buffer
> data.
> -    cudabuffer-buffer-size: 500mb
> -    # The max chunk size that can be sent to the gpu in a single go.
> -    gpu-transfer-size: 50mb
> -    # The timeout limit for batching of packets in microseconds.
> -    batching-timeout: 2000
> -    # The device to use for the mpm.  Currently we don't support
> load balancing
> -    # on multiple gpus.  In case you have multiple devices on your
> system, you
> -    # can specify the device to use, using this conf.  By default we
> hold 0, to
> -    # specify the first device cuda sees.  To find out device-id
> associated with
> -    # the card(s) on the system run "suricata --list-cuda-cards".
> -    device-id: 0
> -    # No of Cuda streams used for asynchronous processing. All
> values > 0 are valid.
> -    # For this option you need a device with Compute Capability >
> 1.0.
> -    cuda-streams: 2
> -
>  ##
>  ## Include other configs
>  ##

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2019-01-29 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 20:22 Peter Müller
2019-01-29 13:11 ` Stefan Schantl [this message]

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=6916aabc790bad7d32974024520436ace5d4a627.camel@ipfire.org \
    --to=stefan.schantl@ipfire.org \
    --cc=development@lists.ipfire.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