search for: scrutinise

Hi Guys, I''ve prepared a simple writeup on how to implement QoS/Trafficshaping using Shorewall and a Hacked Version of Wondershaper-1.1a. After searching through the net for 1+ month, I finally found a solution to my bandwidth hog problem. However, due to the fact that I do not have a personal Webpage I am offering anyone who''s interested this document in a

...rt > breakages more easily, and have a steady progress, rather than a > break-the-world situation. Same for us. The individual patches will be relatively small, this repo was just for context if needed when discussing the smaller patches. > Finally, *every* test change needs to be scrutinised and guaranteed to > make sense. We really dislike spurious test changes, unless we can > prove that the test was unstable to being with, in which case we > change it to a better test. Yep, makes sense. Thanks, -Graham

...have a steady progress, rather than a > > break-the-world situation. > > Same for us. The individual patches will be relatively small, this > repo was just for context if needed when discussing the smaller patches. > > > Finally, *every* test change needs to be scrutinised and guaranteed > to > > make sense. We really dislike spurious test changes, unless we can > > prove that the test was unstable to being with, in which case we > > change it to a better test. > > Yep, makes sense. > > Thanks, > > -G...

..., the XRay runtime, and other related measurements (effect of patching/unpatching of various-sized functions, etc.) As I can certainly publish the numbers I get from the benchmarks, it's not as good as having the benchmarks available somewhere that others can run and verify for themselves (and scrutinise to improve accuracy). I asked on IRC (#llvm) and Chandler suggested that I ask on the list too. Questions: - Is the test-suite repository the right place to put these generated-code benchmarks? - Are there any objections to using a later version of the Google benchmarking library [0] in the test...

...aft-ietf-secsh-filexfer-01.txt). Batch file (-b) support for automated transfers Performance: Speedup DH exchange. OpenSSH should now be significantly faster when connecting use SSH protocol 2. Preferred SSH protocol 2 cipher is AES with hmac-md5. AES offers much faster throughput in a well scrutinised cipher. Bugfixes: stderr handling fixes in SSH protocol 2. Improved interoperability. Client: The client no longer asks for the the passphrase if the key will not be accepted by the server (SSH2_MSG_USERAUTH_PK_OK) Miscellaneous: scp should now work for files > 2GB ssh-keygen can now...

...aft-ietf-secsh-filexfer-01.txt). Batch file (-b) support for automated transfers Performance: Speedup DH exchange. OpenSSH should now be significantly faster when connecting use SSH protocol 2. Preferred SSH protocol 2 cipher is AES with hmac-md5. AES offers much faster throughput in a well scrutinised cipher. Bugfixes: stderr handling fixes in SSH protocol 2. Improved interoperability. Client: The client no longer asks for the the passphrase if the key will not be accepted by the server (SSH2_MSG_USERAUTH_PK_OK) Miscellaneous: scp should now work for files > 2GB ssh-keygen can now...

On Aug 10, 2017, at 3:08 PM, Rafael Avila de Espindola via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Chris Lattner <clattner at llvm.org> writes: > >>> On Aug 10, 2017, at 2:59 PM, Rafael Avila de Espindola <rafael.espindola at gmail.com> wrote: >>> >>> I can find old threads about it, but nothing saying why it was decided >>> that

Hi, We've been working for the last two years on support for ARM's Scalable Vector Extension in LLVM, and we'd like to upstream our work. We've had to make several design decisions without community input, and would like to discuss the major changes we've made. To help with the discussions, I've attached a technical document (also in plain text below) to describe the