From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
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:32:47 -0500 [thread overview]
Message-ID: <20060324173247.GD5400@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200603241243.34687.blaisorblade@yahoo.it>
On Fri, Mar 24, 2006 at 12:43:33PM +0100, Blaisorblade wrote:
> We discussed this time ago, and read the description of the patch:
>
> # Also, as suggested by Jeff, remove a redundant enabling of SIGVTALRM,
> # comprised in the subsequent local_irq_enable(). I'm just a bit dubious if
> # ordering matters there...
Oops, nevermind.
> Note this pre-dates soft interrupts, however.
Shouldn't matter.
> > global-ldt-sem - We should be using mutexes now, not semaphores
>
> That's your patch, but below I drop this.
My patch predates mutexes.
But you still use semaphores, and that should be updated.
> > undo-global-ldt-sem - what's so horrible about the global? it won't
> > be highly contended, so making a single mutex saves memory from every
> > ldt.
>
> For memory: 500 existing processes (a huge number in practice) * 20 byte (and
> I think a semaphore is smaller) = 10 Kbyte. We waste more for the kernel
> stack of 1 thread.
>
> For reason: the compilation problem can be avoided differently (and the
> subsequent patch also merges duplicated code).
>
> I didn't like global_ldt_sem because I felt it unclean; if done for memory
> usage it's another story, but still we need to check this creates no locking
> problem (almost surely no, but I want to look at the code well).
It's simpler. A single global lock is simpler than a lock in every
datastructure.
Jeff
-------------------------------------------------------
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
next prev parent reply other threads:[~2006-03-24 17:31 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
2006-03-24 4:17 ` Jeff Dike
2006-03-24 11:43 ` Blaisorblade
2006-03-24 17:32 ` Jeff Dike [this message]
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=20060324173247.GD5400@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--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 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.