public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Waiman Long <waiman.long@hp.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: James Morris <james.l.morris@oracle.com>,
	Eric Paris <eparis@parisplace.org>,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Chandramouleeswaran,
	Aswin" <aswin@hp.com>, "Norton, Scott J" <scott.norton@hp.com>
Subject: Re: [PATCH v2 1/2] SELinux: reduce overhead of mls_level_isvalid() function call
Date: Fri, 07 Jun 2013 15:50:34 -0400	[thread overview]
Message-ID: <51B2398A.7020104@hp.com> (raw)
In-Reply-To: <51B221F1.7090504@tycho.nsa.gov>

On 06/07/2013 02:09 PM, Stephen Smalley wrote:
>
> Can't you unify this logic with the nearly identical logic below?
>

By separating the logic, we can usually get the best performance out of 
the two separate loops. If code size and maintainability are a bigger 
concern, I can certainly merge the logic. I will try to merge and send 
out a new patch if the performance difference is negligible.

Regards,
Longman

      reply	other threads:[~2013-06-07 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05 21:15 [PATCH v2 1/2] SELinux: reduce overhead of mls_level_isvalid() function call Waiman Long
2013-06-05 21:15 ` [PATCH v2 2/2] SELinux: Increase ebitmap_node size for 64-bit configuration Waiman Long
2013-07-10 18:33   ` Stephen Smalley
2013-07-10 19:59     ` Paul Moore
2013-06-07 18:09 ` [PATCH v2 1/2] SELinux: reduce overhead of mls_level_isvalid() function call Stephen Smalley
2013-06-07 19:50   ` Waiman Long [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=51B2398A.7020104@hp.com \
    --to=waiman.long@hp.com \
    --cc=aswin@hp.com \
    --cc=eparis@parisplace.org \
    --cc=james.l.morris@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=scott.norton@hp.com \
    --cc=sds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox