From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Deepa Dinamani <deepa.kernel@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
Mel Gorman <mgorman@techsingularity.net>,
Tony Jones <tonyj@suse.com>, LKML <linux-kernel@vger.kernel.org>,
linux-audit@redhat.com
Subject: Re: [PATCH] audit: Reduce overhead using a coarse clock
Date: Mon, 10 Jul 2017 10:43:09 -0400 [thread overview]
Message-ID: <20170710144309.GC17720@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAHC9VhSF5wSMXDGY6qi2oYDc1-zHZTdD=qaaF2UPzk_RUy7ngg@mail.gmail.com>
On 2017-07-06 16:25, Paul Moore wrote:
> On Tue, Jul 4, 2017 at 3:41 PM, Deepa Dinamani <deepa.kernel@gmail.com> wrote:
> > On Tue, Jul 4, 2017 at 12:20 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> >> On Tue, Jul 4, 2017 at 2:11 PM, Mel Gorman <mgorman@techsingularity.net> wrote:
> >>>
> >>> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
> >>
> >> Acked-by: Arnd Bergmann <arnd@arndb.de>
> >
> > Acked-by: Deepa Dinamani <deepa.kernel@gmail.com>
> >
> > As already Arnd pointed out, your patch should be fine as that is how
> > it was before my patch. Since nobody saw any problems before my patch,
> > lower granularity should be fine.
>
> Agreed. Mel's patch basically restores the previous behavior while
> keeping the 64-bit timestamp size.
>
> Considering where we are at with the merge window, I'm going to merge
> this into the audit/next branch and not send this up to Linus during
> the current window; while the patch is small, I like to give things
> some time in linux-next before sending them up.
This looks fine to me. Audit has its own event counter so the slightly
coarser granularity of this counter to avoid the overhead shouldn't be a
significant problem.
Reviewed-by: Richard Guy Briggs <rgb@redhat.com>
> paul moore
- RGB
--
Richard Guy Briggs <rgb@redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635
prev parent reply other threads:[~2017-07-10 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 12:11 Mel Gorman
2017-07-04 16:23 ` Deepa Dinamani
2017-07-04 16:53 ` Mel Gorman
2017-07-04 19:20 ` Arnd Bergmann
2017-07-04 19:41 ` Deepa Dinamani
2017-07-06 20:25 ` Paul Moore
2017-07-06 23:31 ` Mel Gorman
2017-07-10 14:43 ` Richard Guy Briggs [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=20170710144309.GC17720@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=paul@paul-moore.com \
--cc=tonyj@suse.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
all inboxes | Powered by JetHome®