public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Stanislawski <t.stanislaws@samsung.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-security-module@vger.kernel.org, m.szyprowski@samsung.com,
	kyungmin.park@samsung.com, r.krypa@samsung.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFCv2] security: smack: add a hash table to quicken smk_find_entry()
Date: Fri, 02 Aug 2013 11:00:44 +0200	[thread overview]
Message-ID: <51FB753C.1080809@samsung.com> (raw)
In-Reply-To: <51FAF62F.9090301@schaufler-ca.com>

On 08/02/2013 01:58 AM, Casey Schaufler wrote:
> On 6/27/2013 2:11 PM, Casey Schaufler wrote:
>> On 6/11/2013 5:55 AM, Tomasz Stanislawski wrote:
>>> This patch adds a hash table to quicken searching of a smack label by its name.
>>>
>>> Basically, the patch improves performance of SMACK initialization.  Parsing of
>>> rules involves translation from a string to a smack_known (aka label) entity
>>> which is done in smk_find_entry().

[snip]

>> I will take this into my tree after changing SMACK_HASH_SLOTS to 16.
>>
>> Acked-by: Casey Schaufler <casey@schaufler-ca.com>
> 
> Applied to git://git.gitorious.org/smack-next/kernel.git#smack-for-3.12
> 
> Rebasing was required. The change has been tested.
> 
> 

Hi,
Thanks for merging the patch.
BTW. Do you have comments about:

http://thread.gmane.org/gmane.linux.kernel.lsm/19650

Here I posted all of the acceptable patches rebased on smack-next.
Moreover, I added measurements of impact of patches on both time and
memory consumption.
There were no comments about this patchset. Maybe something was lost?

Regards,
Tomasz Stanislawski



      reply	other threads:[~2013-08-02  9:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 12:55 [RFCv2] security: smack: add a hash table to quicken smk_find_entry() Tomasz Stanislawski
2013-06-11 12:55 ` Tomasz Stanislawski
2013-06-12  5:11   ` Casey Schaufler
2013-06-12 13:40     ` Tomasz Stanislawski
2013-06-13  4:14       ` Casey Schaufler
2013-06-27 21:11   ` Casey Schaufler
2013-08-01 23:58     ` Casey Schaufler
2013-08-02  9:00       ` Tomasz Stanislawski [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=51FB753C.1080809@samsung.com \
    --to=t.stanislaws@samsung.com \
    --cc=casey@schaufler-ca.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=r.krypa@samsung.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