All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert Cahalan <albert@users.sf.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [patch] exec-shield-nx-2.6.9-A1
Date: 17 Oct 2004 19:08:50 -0400	[thread overview]
Message-ID: <1098054529.2666.14326.camel@cube> (raw)
In-Reply-To: <20041017203055.GA10403@elte.hu>

On Sun, 2004-10-17 at 16:30, Ingo Molnar wrote:

> > [...] One might guess from CAP_SYS_NICE that the feature has now
> > become hopelessly slow. [...]
> 
> (thank you for the kind words, it is always heartening to read your
> mails! I too wish you good luck with your projects.)

:-)

Well, CAP_SYS_NICE does kind of imply that there is
an issue with CPU time, doesn't it? I didn't see any
code that would change performance, so I suppose you
figure that wchan is already too slow?

CAP_SYS_ADMIN is the misc. dumping ground normally.




  reply	other threads:[~2004-10-17 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 20:11 [patch] exec-shield-nx-2.6.9-A1 Albert Cahalan
2004-10-17 20:30 ` Ingo Molnar
2004-10-17 23:08   ` Albert Cahalan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-17  9:53 Ingo Molnar
2004-10-20 17:23 ` Sami Farin

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=1098054529.2666.14326.camel@cube \
    --to=albert@users.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.