linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Antoine Martin <antoine@nagafix.co.uk>
Subject: Re: [uml-devel] Re: TLS support - status - need for re-testing
Date: Fri, 24 Mar 2006 12:43:50 +0100	[thread overview]
Message-ID: <200603241243.51087.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20060324015120.GA8104@ccure.user-mode-linux.org>

On Friday 24 March 2006 02:51, Jeff Dike wrote:
> On Fri, Mar 24, 2006 at 12:44:05AM +0100, Blaisorblade wrote:
> > Yes, that is true, but meanwhile give a testing to them, especially
> > regressio test the new patches. I can't merge new patches in until I'm
> > sure they don't cause regressions.

> OK, I give it a thumbs-up on a first boot - it's running my FC5
> filesystem without any trouble.  I'll keep playing with it and let you
> know of any trouble.

With the x86-64 host hack, it works here too.

To do good stress-testing, I've actually noticed the existing problems when I 
started running apache benchmark (with apache using multithreading, i.e. 
mpm_worker_thread).

I run it like:

ab2 -n 100 -c 10 -t 30 -v 1 Sarge/

where -n, -c and -t are simple parameters which can be tuned at will. (It 
could be simply ab on your distro).

> Attached is a tarball of the patches merged after the patches I have
> planned for 2.6.17.  Nothing major, just some fuzz, some Makefile
> rejections, and rejections from some whitespace cleanup in
> kernel/skas/process_kern.c.

Will look at.
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

		
___________________________________ 
Yahoo! Messenger with Voice: chiama da PC a telefono a tariffe esclusive 
http://it.messenger.yahoo.com



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2006-03-24 11:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23  2:17 [uml-devel] TLS support - status - need for re-testing Blaisorblade
2006-03-23 11:29 ` [uml-devel] " Antoine Martin
2006-03-23 21:14 ` Jeff Dike
2006-03-23 23:44   ` Blaisorblade
2006-03-24  1:51     ` Jeff Dike
2006-03-24 10:39       ` Antoine Martin
2006-03-24 11:44         ` Blaisorblade
2006-03-24 11:43       ` Blaisorblade [this message]
2006-03-24  4:17     ` Jeff Dike
2006-03-24 11:43       ` Blaisorblade
2006-03-24 17:32         ` Jeff Dike
2006-03-24 18:44           ` Blaisorblade

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=200603241243.51087.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=antoine@nagafix.co.uk \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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