linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Seymour, Shane M" <shane.seymour@hp.com>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Kai.Makisara@kolumbus.fi" <Kai.Makisara@kolumbus.fi>,
	"James E.J. Bottomley (JBottomley@parallels.com)"
	<JBottomley@parallels.com>,
	"Laurence Oberman (loberman@redhat.com)" <loberman@redhat.com>
Subject: Re: [RFC] implementing tape statistics single file vs multi-file in sysfs
Date: Wed, 11 Feb 2015 11:32:01 +0000	[thread overview]
Message-ID: <20150211113200.GA5864@localhost.localdomain> (raw)
In-Reply-To: <20150210223027.GA27269@kroah.com>

On Wed, Feb 11, 2015 at 06:30:27AM +0800, Greg KH wrote:
> On Tue, Feb 10, 2015 at 02:27:20PM +0000, Bryn M. Reeves wrote:
> > On Sat, Feb 07, 2015 at 12:07:43PM +0800, Greg KH wrote:
> > 
> > $ cat /sys/fs/selinux/avc/cache_stats 
> > lookups hits misses allocations reclaims frees
> > 18938916 18921707 17209 17209 17328 22215
> > 38164283 38146514 17769 17769 16800 19049
> > 18078108 18056991 21117 21117 21344 19305
> > 15168204 15150079 18125 18125 17776 13149
> > 0 0 0 0 0 0
> > 0 0 0 0 0 0
> > 0 0 0 0 0 0
> > 0 0 0 0 0 0
> > 
> > $ cat /sys/fs/selinux/avc/hash_stats
> > entries: 506
> > buckets used: 290/512
> > longest chain: 5
> 
> Ugh, those look like they should be debugfs interfaces.  Thanks, I'll
> add them to my list of things to nag people about...

Actually looking properly these are outside sysfs:

$ mount | grep selinux
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)

So everything below the mount point is in their own vfstype.

Regards,
Bryn.


      reply	other threads:[~2015-02-11 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06  0:20 [RFC] implementing tape statistics single file vs multi-file in sysfs Seymour, Shane M
     [not found] ` <DDB9C85B850785449757F9914A034FCB3BF3EADA-4I1V4pQFGigSZAcGdq5asR6epYMZPwEe5NbjCUgZEJk@public.gmane.org>
2015-02-06  9:13   ` Bryn M. Reeves
     [not found]     ` <20150206091354.GA1143-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-02-06 13:01       ` Greg KH
2015-02-06 12:59   ` Greg KH
     [not found]     ` <20150206125916.GB26247-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-02-06 15:41       ` Bryn M. Reeves
2015-02-07  4:07         ` Greg KH
2015-02-08  2:27           ` Laurence Oberman
2015-02-08  2:45             ` Greg KH
2015-02-08  8:32               ` "Kai Mäkisara (Kolumbus)"
     [not found]               ` <20150208024506.GC15396-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-02-08 17:35                 ` James Bottomley
     [not found]           ` <20150207040743.GB29944-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-02-10 14:27             ` Bryn M. Reeves
     [not found]               ` <20150210142719.GA1437-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2015-02-10 22:30                 ` Greg KH
2015-02-11 11:32                   ` Bryn M. Reeves [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=20150211113200.GA5864@localhost.localdomain \
    --to=bmr@redhat.com \
    --cc=JBottomley@parallels.com \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=loberman@redhat.com \
    --cc=shane.seymour@hp.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;
as well as URLs for NNTP newsgroup(s).