public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: warthog9@kernel.org, linux-kernel@vger.kernel.org, users@kernel.org
Subject: Re: [kernel.org users] [KORG] Taking hera down to deal with the load issues
Date: Fri, 19 Aug 2011 07:08:23 -0400	[thread overview]
Message-ID: <1313752103.3243.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20110818.221433.2023110799070604982.davem@davemloft.net>

On Thu, 2011-08-18 at 22:14 -0700, David Miller wrote:
> From: "J.H." <warthog9@kernel.org>
> Date: Wed, 17 Aug 2011 01:05:56 -0700
> 
> > This second kernel is at least, so far, acting a lot closer to what I'd
> > expect from hera, but the disk cache is still filling.  I'm going to
> > keep an eye on it for a bit longer tonight.  As a note, the only
> > difference between the first 3.1-rc1 kernel and the second, that is
> > currently running, was the explicit disabling of IMA and recompiling the
> > kernel.
> 
> I wonder if the IMA bits are generating crypto hashes for every file
> modification done on the machine.

Possibly, but IMA doesn't recalculate the hash for every modification.
Without the boot command line parameter 'ima_tcb', nothing should be
measured.  With 'ima_tcb', only files accessed by root are measured and
then only re-measured, if flushed from the inode cache or has been
marked changed, which occurs on __fput(), not every write.

thanks,

Mimi


      reply	other threads:[~2011-08-19 11:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16 23:27 [KORG] Taking hera down to deal with the load issues J.H.
2011-08-17  8:05 ` [kernel.org users] " J.H.
2011-08-17 18:37   ` Jan Kara
2011-08-18 18:52     ` J.H.
2011-08-19  5:14   ` David Miller
2011-08-19 11:08     ` Mimi Zohar [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=1313752103.3243.33.camel@localhost.localdomain \
    --to=zohar@linux.vnet.ibm.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=users@kernel.org \
    --cc=warthog9@kernel.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