mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@openvz.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: James Morris <jmorris@namei.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org, Greg KH <greg@kroah.com>,
	Stephen Smalley <sds@epoch.ncsc.mil>,
	Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2)
Date: Fri, 14 Mar 2008 18:07:58 +0300	[thread overview]
Message-ID: <47DA94CE.9090101@openvz.org> (raw)
In-Reply-To: <20080314143752.GE9741@sergelap.austin.ibm.com>

[snip]

>> The # of rules usually has a linear dependency on the number of containers
>> (each of then has to have an access to /dev/null,zero,random at least), so
>> having 100 containers we will have to scan through a 300-entries list.
> 
> Oh no, the rules are stored per-container, so it sounds like you're
> saying 3 entries per container?

Oops :) I've missed that part :(

>> I'd
>> vote for a hash table or a radix/binary/rb tree for that. Or any other way
>> for non-linear search you can provide :)
> 
> I'm fine with that, but not for 3 rules  :)

So am I :) Anyway - if someday this will grow up to tens of entries turning
it into a more scalable lookup would be easy.

> -serge
> 


  reply	other threads:[~2008-03-14 15:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  3:27 Serge E. Hallyn
2008-03-13  9:25 ` James Morris
2008-03-13 13:18   ` Serge E. Hallyn
2008-03-13 13:50     ` James Morris
2008-03-13 14:38       ` Serge E. Hallyn
2008-03-13 22:27         ` James Morris
2008-03-13 22:46           ` Serge E. Hallyn
2008-03-13 23:49             ` James Morris
2008-03-14  1:41               ` Serge E. Hallyn
2008-03-14  4:47                 ` Greg KH
2008-03-14 13:54                   ` Serge E. Hallyn
2008-03-14 13:58                     ` Pavel Emelyanov
2008-03-14 15:45                       ` Serge E. Hallyn
2008-03-14 15:54                         ` Pavel Emelyanov
2008-03-14 16:57                         ` Stephen Smalley
2008-03-14  9:28                 ` Pavel Emelyanov
2008-03-14 13:58                   ` Serge E. Hallyn
2008-03-14 14:05                     ` Pavel Emelyanov
2008-03-14 14:37                       ` Serge E. Hallyn
2008-03-14 15:07                         ` Pavel Emelyanov [this message]
2008-03-14 14:12                     ` Paul Menage
2008-03-14 14:42                       ` Serge E. Hallyn
2008-03-16  0:59                         ` Paul Menage
2008-03-14  2:51               ` Casey Schaufler
2008-03-14  9:16 ` Paul Menage
2008-03-14 14:05   ` Serge E. Hallyn
2008-03-14 14:15     ` Paul Menage
2008-03-14 14:35       ` Serge E. Hallyn
2008-03-16  0:57         ` Paul Menage
2008-03-14  9:18 ` Paul Menage
2008-03-14 14:00   ` Serge E. Hallyn

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=47DA94CE.9090101@openvz.org \
    --to=xemul@openvz.org \
    --cc=casey@schaufler-ca.com \
    --cc=greg@kroah.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    --cc=serue@us.ibm.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®