{"push_id":1202115988,"size":1,"distinct_size":1,"ref":"refs/heads/raidz_fix1","head":"997b49ff392912c2dc76eef057fd489d2c295443","before":"125506b20926c065b2bbce0af75934567c23ae32","commits":[{"sha":"997b49ff392912c2dc76eef057fd489d2c295443","author":{"name":"Gvozden Neskovic","email":"89b6946db64cd5770ca50b2bd89195148bde383d@gmail.com"},"message":"Fixes and enhancements of SIMD raidz parity\n\n- Writer lock is now acquired when zfs_vdev_raidz_impl_set() is invoked for user\nparameter change.\n\n- Trailing whitespace is removed from user specified parameter, to enhance\nexperience when using commands that add newline, e.g. `echo`\n\n- To enable better insight in what parity implementation is being used when\n[fastest] option is selected for `zfs_vdev_raidz_impl` parameter, following\nchanges are made:\n\t- An unique ID is assigned to every physical parity method. Each parity\n\timplementation consists of 10 distinct parity methods.\n\t- Methods of the [fastest] implementation will have IDs that indicate\n\tphysical implementation used (determined by a micro-benchmark).\n\t- List of all supported parity methods, with ID and relative performance,\n\tis available in `/proc/spl/kstat/zfs/vdev_raidz_bench`\n\n- raidz_test: remove dependency on `getrusage()` and RUSAGE_THREAD, Issue #4813\n\n- Minor fixes and cleanups\n\nSigned-off-by: Gvozden Neskovic <neskovic@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ironMann/zfs/commits/997b49ff392912c2dc76eef057fd489d2c295443"}]}
{"actor":{"display_login":"ironMann"}}