Re: what's next for the linux kernel?

[Nikita Danilov]

Luke Kenneth Casson Leighton writes:
 > On Sun, Oct 02, 2005 at 08:27:45PM -0500, Chase Venters wrote:
 > 
 > > The bottom line is that the application developers need to start being clever 
 > > with threads. 
 > 
 >  yep!  ah.  but.  see this:
 > 
 >  http://lists.samba.org/archive/samba-technical/2004-December/038300.html
 > 
 >  and think what would happen if glibc had hardware-support for
 >  semaphores and mutexes.

Let me guess... nothing? Overhead of locking depends on data-structures
used by application/library and their access patterns: one thread has to
wait for another to finish with the shared resource. Implementing
locking in hardware is going to change nothing here (barring really
stupid implementations of locking primitives). Especially as we are
talking about blocking primitives, like pthread semaphore or mutex: an
entry into the scheduler will by far outweigh any advantages of
raw-metal synchronization.

 > 
 > > I think I remember some interesting rumors about Perl 6, for 
 > > example, including 'autothreading' support - the idea that your optimizer 
 > > could be smart enough to identify certain work that can go parallel.

Fortran people automatically parallelize loops for a _long_ time.

 > 
 >  http://www.ics.ele.tue.nl/~sander/publications.php
 >  http://portal.acm.org/citation.cfm?id=582068
 >  http://csdl.computer.org/comp/proceedings/acsd/2003/1887/00/18870237.pdf
 > 
 >  to get the above references, put in "holland parallel code
 >  analysis tools" into google.com.

PS: I wonder why Luke Kenneth Casson Leighton, Esq., while failing to
spell the Grandeur of his Appellative with the full Capitalization in
not a single From header humble readers of this Thread have a rare Honor
to witness, insists on referring to his interlocutors in minuscule only?

Does this correlate with an abnormally frequent usage of word
"condescending" in this discussion?

Nikita.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/