All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <jmorris@redhat.com>,
	selinux@tycho.nsa.gov, Karl MacMillan <kmacmillan@tresys.com>,
	Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Subject: Re: [RFC][PATCH 0/3] Reduce number of avtab nodes
Date: Mon, 1 Aug 2005 15:22:12 +0100	[thread overview]
Message-ID: <20050801142212.GC10132@lkcl.net> (raw)
In-Reply-To: <1122903665.6573.281.camel@moss-spartans.epoch.ncsc.mil>

On Mon, Aug 01, 2005 at 09:41:05AM -0400, Stephen Smalley wrote:
> On Sun, 2005-07-31 at 11:59 -0400, James Morris wrote:
> > With these patches, on a 64-bit system, after boot:
> > 
> >   
> >             #objs  objsize   kernmem
> > Targeted:
> >   Before:  237888       40     9.1MB
> >   After:    19968       24     468KB
> > 
> > Strict:
> >   Before:  571680       40   21.81MB
> >   After:   221052       24    5.06MB
> 
> Ok, this along with the data I posted for 32-bit is certainly
> encouraging as far as memory savings are concerned.  Things that we need
> to resolve before committing/upstreaming these changes include:
> 
> - We need to measure the performance impact of the changes on the
> kernel, if any, and possibly optimize the compute_av code if it is
> measurable.

 little story for you that is comp-sci related [which if
 you're aware of these sorts of things i humbly apologise for
 mentioning - grandmas, eggs, suck, sorry :) ]

 andrew tridgell wrote an upper-case / lower-case unicode
 converter for samba.  it wasn't a 16-bit lookup table,
 because 65536 * 2 equals 128kbytes which is _way_ more memory
 than can fit into a first level cache of some processors.
 consequently, performance of a lookup table would be crap.
 what he wrote instead was a small algorithm with lookup ranges.
 it was heaps faster.
 
 anyway, what you're doing is reminiscent of that and so
 i thought i should mention it and i invite you to consider
 performing some tests on hardware ranging from ARM 2-400mhz
 with the usual shit-for-brains caches through PIIIs and
 AMD K7s to P4s, picking the most likely candidates where
 it's going to matter or even possibly consider offering /
 enabling / disabling different optimisations depending on
 the processor target (CONFIG_xxx).

 again though i respectfully ask you to totally ignore me
 should you have considered these things already - comp-sci
 being what it is.

 l.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-08-01 14:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 16:49 [RFC][PATCH 0/3] Reduce number of avtab nodes Stephen Smalley
2005-07-29 17:16 ` [RFC][PATCH 1/3] " Stephen Smalley
2005-07-29 17:22 ` [RFC][PATCH 2/3] " Stephen Smalley
2005-07-29 17:23 ` [RFC][PATCH 3/3] " Stephen Smalley
2005-07-29 18:01 ` [RFC][PATCH 0/3] " Stephen Smalley
2005-07-29 19:05 ` James Morris
2005-07-30  4:20 ` James Morris
2005-07-30 19:13   ` Joshua Brindle
2005-07-31 15:59 ` James Morris
2005-08-01 13:41   ` Stephen Smalley
2005-08-01 14:22     ` Luke Kenneth Casson Leighton [this message]
2005-08-01 14:58     ` Joshua Brindle
2005-08-01 15:04       ` Stephen Smalley
2005-08-01 15:09       ` Stephen Smalley
2005-08-01 15:32         ` Joshua Brindle
2005-08-04  7:57         ` Russell Coker
2005-08-04 14:35           ` Valdis.Kletnieks
2005-08-04 14:38             ` Stephen Smalley
2005-08-04 15:38               ` Joshua Brindle
2005-08-04 15:45                 ` Stephen Smalley
2005-08-04 15:52                   ` Joshua Brindle
2005-08-04 15:46               ` Russell Coker
2005-08-02 16:43     ` Stephen Smalley
2005-08-02 20:50       ` Stephen Smalley
2005-08-04 12:52     ` Stephen Smalley
2005-08-04 16:14       ` Stephen Smalley
2005-08-08 18:42         ` Stephen Smalley
2005-08-04  7:42 ` Russell Coker
2005-08-04 13:25   ` Stephen Smalley

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=20050801142212.GC10132@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=jmorris@redhat.com \
    --cc=kmacmillan@tresys.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.