From: James Morris <jmorris@redhat.com>
To: Kaigai Kohei <kaigai@ak.jp.nec.com>
Cc: "akpm@osdl.org" <akpm@osdl.org>,
Stephen Smalley <sds@epoch.ncsc.mil>,
Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SELinux performance improvement with RCU
Date: Mon, 27 Sep 2004 11:51:12 -0400 (EDT) [thread overview]
Message-ID: <Xine.LNX.4.44.0409271146550.21876-100000@thoron.boston.redhat.com> (raw)
In-Reply-To: <200409271057.i8RAvcA1007873@mailsv.bs1.fc.nec.co.jp>
On Mon, 27 Sep 2004, Kaigai Kohei wrote:
> Because this patch depends on two external function: atomic_inc_return()
> and list_replace_rcu(), I was waiting for those functions to be merged
> into 2.6.9-rc2-mm2 tree.
> Please apply this.
Kaigai,
Have you addressed the lockups which Stephen Smalley reported to you when
testing this code?
You also have not addressed issues raised regarding low end performance.
Also, the patch has not been fully vetted by the maintainers (Stephen and
myself).
- James
--
James Morris
<jmorris@redhat.com>
prev parent reply other threads:[~2004-09-27 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 10:57 [PATCH] SELinux performance improvement with RCU Kaigai Kohei
2004-09-27 15:51 ` James Morris [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=Xine.LNX.4.44.0409271146550.21876-100000@thoron.boston.redhat.com \
--to=jmorris@redhat.com \
--cc=akpm@osdl.org \
--cc=kaigai@ak.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@epoch.ncsc.mil \
/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).