public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: allow unlimited backlog queue
Date: Wed, 15 Jan 2014 12:24:04 -0500	[thread overview]
Message-ID: <1459080.Bs1WkWcKGH@x2> (raw)
In-Reply-To: <20140115171228.GF23247@madcap2.tricolour.ca>

On Wednesday, January 15, 2014 12:12:28 PM Richard Guy Briggs wrote:
> > > Eric and I discussed bumping up the default.  I would have liked to have
> > > seen somewhere between 320 and 512, but that default would make the
> > > embedded folks unhappy and I don't really want to get into the more
> > > complex idea of having it guess what type of system it is trying to
> > > configure to give a smaller number for embedded systems (which aren't
> > > all small) and bigger ones to servers (which aren't all big).
> >
> > What about making it a compile time choice in the kernel config? I
> > suggested  making a compile time option, distributions can bump that up
> > to 512, the default is enough and it can be tuned. Embedded can make the
> > default whatever they want, too.
> 
> Eric and I had discussed that too, and I understand there is
> considerable pushback to adding to kconfig, so that option would be
> harder to get accepted.

So how does making the backlog value of 0 be unlimited solve the problem?

-Steve

  reply	other threads:[~2014-01-15 17:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 22:59 [PATCH] audit: allow unlimited backlog queue Richard Guy Briggs
2014-01-14 23:04 ` Richard Guy Briggs
2014-01-15 13:03   ` Steve Grubb
2014-01-15 16:46     ` Richard Guy Briggs
2014-01-15 16:57       ` Steve Grubb
2014-01-15 17:12         ` Richard Guy Briggs
2014-01-15 17:24           ` Steve Grubb [this message]
2014-01-15 17:31             ` Richard Guy Briggs
2014-01-15  1:19 ` Gao feng
2014-01-15 12:53 ` Steve Grubb
2014-01-15 16:50   ` Richard Guy Briggs

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=1459080.Bs1WkWcKGH@x2 \
    --to=sgrubb@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=rgb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox