Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Kaz Kylheku <kaz@kylheku.com> |
|---|---|
| Newsgroups | comp.arch |
| Subject | Re: More about waitfree and lockfree |
| Date | 2014-04-23 23:13 +0000 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <20140423160332.322@kylheku.com> (permalink) |
| References | <lj7116$3c3$5@news.albasani.net> <cd1edc26-da1f-40e1-ad24-7979e621e935@googlegroups.com> |
On 2014-04-23, MitchAlsup <MitchAlsup@aol.com> wrote: > On Tuesday, April 22, 2014 7:20:54 PM UTC-5, aminer wrote: >> Hello... > > I have a suggestion for you. > > Continue to post, but never change the subject line again. Just add and add and > add posts to the current open post. Even if you come out with a new version > (like in 3 hours or so), just leave it all in one thread. All of it. > > Did you even notice that everyone else in this newsgroup happens to maintain > threads and adds to them as they feel fit. But you seem to spew new posts > over a wide berth with virtually no changes. > > I understand you feel justifiably proud of your achievements, but cut the SPAM, > please. > > By the way, have you noticed how few reponses you are getting? aminer's ideas are not coherently presented in a structure which takes a low amount of effort to understand them. The incremental "status reports" make little sense to anyone who has not been eagerly been following the progress in detail from the beginning. The work appears to consists of empirical experimentation with a changing reference implementation of some locks, in combination with some tests, on particular hardware configuration. There is no compelling reason to believe that the results have any general value that translates to the real world. Distributing .zip files is an outdated method. The experimentation could easily be summarized in the commit comments in a git repository. Anyone who cares about the progress could dig through the history, whose checking comments explain what was changed, what was the intent of those changes, and how they actually impacted the benchmarks. Over the course of several months, the author could dig through this history, and write a concise paper summarizing the empirical findings.
Back to comp.arch | Previous | Next — Previous in thread | Find similar | Unroll thread
More about waitfree and lockfree aminer <aminer@toto.net> - 2014-04-22 20:21 -0700
Re: More about waitfree and lockfree MitchAlsup <MitchAlsup@aol.com> - 2014-04-22 18:07 -0700
Re: More about waitfree and lockfree "Chris M. Thomasson" <no@spam.invalid> - 2014-04-23 12:52 -0700
Re: More about waitfree and lockfree aminer <aminer@toto.net> - 2014-04-23 15:58 -0700
Re: More about waitfree and lockfree aminer <aminer@toto.net> - 2014-04-23 16:08 -0700
Re: More about waitfree and lockfree aminer <aminer@toto.net> - 2014-04-23 16:19 -0700
Re: More about waitfree and lockfree aminer <aminer@toto.net> - 2014-04-23 16:32 -0700
Re: More about waitfree and lockfree aminer <aminer@toto.net> - 2014-04-23 16:41 -0700
Re: More about waitfree and lockfree Kaz Kylheku <kaz@kylheku.com> - 2014-04-23 23:13 +0000
csiph-web