- 29 Mar, 2016 20 commits
-
-
Jian Yu authored
On some customers' systems, the kernel was compiled with HZ defined to 100, instead of 1000. This improves performance for HPC applications. However, to use these systems with Lustre, customers have to re-build Lustre for the kernel because Lustre directly uses the defined constant HZ. Since kernel 2.6.21, some non-HZ dependent timing APIs become non- inline functions, which can be used in Lustre codes to replace the direct HZ access. These kernel APIs include: jiffies_to_msecs() jiffies_to_usecs() jiffies_to_timespec() msecs_to_jiffies() usecs_to_jiffies() timespec_to_jiffies() And here are some samples of the replacement: HZ -> msecs_to_jiffies(MSEC_PER_SEC) n * HZ -> msecs_to_jiffies(n * MSEC_PER_SEC) HZ / n -> msecs_to_jiffies(MSEC_PER_SEC / n) n / HZ -> jiffies_to_msecs(n) / MSEC_PER_SEC n / HZ * 1000 -> jiffies_to_msecs(n) This patch replaces the direct HZ access in the libcfs module. Signed-off-by:
Jian Yu <jian.yu@intel.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5443 Reviewed-on: http://review.whamcloud.com/11993Reviewed-by:
Nathaniel Clark <nathaniel.l.clark@intel.com> Reviewed-by:
James Simmons <uja.ornl@gmail.com> Reviewed-by:
Oleg Drokin <oleg.drokin@intel.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Liang Zhen authored
initialise lock-class for each sublock of cfs_percpt_lock to eliminate false alarm ""possible recursive locking detected" Signed-off-by:
Liang Zhen <liang.zhen@intel.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6432 Reviewed-on: http://review.whamcloud.com/14368Reviewed-by:
James Simmons <uja.ornl@yahoo.com> Reviewed-by:
Andreas Dilger <andreas.dilger@intel.com> Reviewed-by:
-
James Simmons authored
Move the CPT handling declartions out of libcfs_private.h to libcfs_cpu.h where it belongs. Signed-off-by:
frank zago <fzago@cray.com> Signed-off-by:
John L. Hammond <john.hammond@intel.com> Reviewed-by:
-
James Simmons authored
The functions cfs_percpt_current() and cfs_percpt_index() are not used anywhere. Remove it. Signed-off-by:
-
James Simmons authored
libcfs contains functions to perform atomic memory operations. These functions have never been used so remove them. Signed-off-by:
-
James Simmons authored
Use signal_pending() directly instead of a one line function wrapper. Signed-off-by:
Dmitry Eremin <dmitry.eremin@intel.com> Reviewed-by:
-
James Simmons authored
A few function declarations are in libcfs.h that are not needed. Signed-off-by:
-
Oleg Drokin authored
Commit b8ff756bc351 ("staging: lustre: libcfs: merge code from libcfs_ioctl into libcfs_ioctl_getdata") introduced a problem copying just a single pointer worth of data from userspace instead of whole libcfs_ioctl_hdr structure. Adjust the copying amount. Signed-off-by:Oleg Drokin <green@linuxhacker.ru> Acked-by:
James Simmons <jsimmons@infradead.org> Signed-off-by:
-
Andreas Dilger authored
Use alloc_page() and use cfs_crypto_hash_update_page() to compute the hash instead of cfs_crypto_hash_digest(), since tgt_checksum_bulk() computes the hash by page anyway. Signed-off-by:
Alexander Boyko <alexander_boyko@xyratex.com> Reviewed-by:
Bob Glossman <bob.glossman@intel.com> Reviewed-by:
-
Andreas Dilger authored
Set cfs_crypto_hash_speeds[X] result to the actual error instead of -1. Make the error message more clear and informative. Signed-off-by:
-
Andreas Dilger authored
Only print info about the crypto performance when no error is encounter. Signed-off-by:
-
Andreas Dilger authored
Move memory allocation from cfs_crypto_test_hashes() into the function cfs_crypto_performance_test(). Signed-off-by:
-
Andreas Dilger authored
Return a real error code, -ENOENT, instead of a -1. Signed-off-by:
-
Andreas Dilger authored
Change cfs_crypto_hash_final() to always clean up the hash descrptor instead of not doing this in error cases. All of the callers were just calling cfs_crypto_hash_final() immediately to clean up the descriptor anyway, and the old behaviour is unlike other init/fini functions, and prone to memory leaks and other incorrect usage. The callers can call cfs_crypto_digest_size() to determine the hash size in advance if needed, and avoid complexity in cfs_crypto_hash_final(). Signed-off-by:
-
Andreas Dilger authored
Fix the cfs_crypto_hash_* functions to take enum cfs_crypto_hash_alg as the algorithm type, instead of an unsigned char. Signed-off-by:
-
Andreas Dilger authored
Change the aligment of some of the functions. Signed-off-by:
-
Andreas Dilger authored
Add CFS_HASH_ALG_UNKOWN for unknown hash names instead of using "0xFF" directly. Define the max digestsize the cfs crypto api can handle. Signed-off-by:
-
Andreas Dilger authored
For the crypto algorthim type use the same name hash_alg everywhere. Signed-off-by:
-
Andreas Dilger authored
Add comment blocks for cfs_crypto_hash_*() in linux-crypto.c and libcfs_crypto.h. Delete obsolete comment about shash handling in cfs_crypto_hash_alloc(). Signed-off-by:
-
Andreas Dilger authored
Remove <libcfs/libcfs_crypto.h> from <libcfs/libcfs.h> and only include it into the places where it is actually needed. This works out to be the same places as <obd_cksum.h>, so put it there. Signed-off-by:
-
- 28 Mar, 2016 20 commits
-
-
Daeseok Youn authored
fix checkpatch.pl warning about 'Logical continuations should be on the previous line' in dgnc_neo.c file. I think the 'force' need to check first, because if the 'force' is true, it doesn't need to call another function call. Signed-off-by:
Daeseok Youn <daeseok.youn@gmail.com> Signed-off-by:
-
Daeseok Youn authored
fix checkpatch.pl warning about 'line over 80 characters' in dgnc_neo.c Signed-off-by:
-
Daeseok Youn authored
TtyRefCnt was not used anywhere in dgnc. Signed-off-by:
-
Daeseok Youn authored
fix checkpatch.pl warning about CamelCase Signed-off-by:
-
Nicholas Sim authored
Remove braces from one branch of if statement where both branches only have a single line of code, as suggested in Documentation/CodingStyle Signed-off-by:
Nicholas Sim <nicholassimws@gmail.com> Signed-off-by:
-
Nicholas Sim authored
Added braces on else arm of if statement where if arm already has braces as suggested for clarity in Documentation/CodingStyle Signed-off-by:
-
Nicholas Sim authored
Remove unnecessary return statements from last lines of void function call (several) Signed-off-by:
-
Parth Sane authored
Using comparison to false and true is error prone. Fixed multiple warnings as per checkpatch guidelines. Signed-off-by:
Parth Sane <laerdevstudios@gmail.com> Signed-off-by:
-
Claudiu Beznea authored
This patch covers wiphy_register() failures in wlan_create_wiphy() from cfg80211.c by calling wiphy_free() for the correspondent struct wiphy allocated structure. Signed-off-by:
Claudiu Beznea <claudiu.beznea@gmail.com> Signed-off-by:
-
Daeseok Youn authored
fix checkpatch.pl warning about CamelCase. Signed-off-by:
-
Ksenija Stanojevic authored
Fix following sparse warning: warning: cast to restricted __be16 Signed-off-by:
Ksenija Stanojevic <ksenija.stanojevic@gmail.com> Signed-off-by:
-
PrasannaKumar Muralidharan authored
Remove unnecessary __cplusplus check in header files as it is not required. Signed-off-by:
PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com> Signed-off-by:
-
Okash Khawaja authored
Compiling speakup driver with sparse produces following warning: drivers/staging/speakup/serialio.c:22:9: warning: incorrect type in initializer (different base types) drivers/staging/speakup/serialio.c:22:9: expected unsigned int [unsigned] flags drivers/staging/speakup/serialio.c:22:9: got restricted upf_t This patch fixes it. Signed-off-by:
Okash Khawaja <okash.khawaja@gmail.com> Acked-by:
Samuel Thibault <samuel.thibault@ens-lyon.org> Signed-off-by:
-
H Hartley Sweeten authored
This function calls some helper functions to convert the counter variant specific clock select bits into the generic enum ni_gpct_clock_source_bits equivelent. These helper functions currently BUG() if the clock select bits are invalid. It then calls ni_tio_clock_period_ps() to figure out the clock period based on the generic clock source. This function could also BUG() if the prescale bits are invalid. In reality this should never happen but refactor the code to return -EINVAL instead and remove the BUG() checks. These functions are also called by ni_tio_set_sync_mode(). When this function is called by ni_tio_set_clock_src() the counter select bits have already been validated. Signed-off-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Reviewed-by:
Ian Abbott <abbotti@mev.co.uk> Signed-off-by:
-
H Hartley Sweeten authored
This BUG() can never happen. The previous ni_tio_has_gate2_registers() check will have already caused the function to return -EINVAL. Signed-off-by:
-
H Hartley Sweeten authored
The (*insn_config) functions are supposed to return an errno or the number of 'data' values used for the instruction (insn->n). Currently this function returns an errno or 0. Fix the function to work like the core expects. Signed-off-by:
-
H Hartley Sweeten authored
This function calls some helper functions to convert the counter variant specific gate select bits into the generic enum ni_gpct_clock_source_bits equivelent. These helper functions currently BUG() if the gate select bits are invalid. This should never happen but refactor the code to return -EINVAL instead and remove the BUG() checks. Signed-off-by:
-
H Hartley Sweeten authored
Refactor the functions that determine the clock source bits so that they return -EINVAL if the clock source is invalid. Pass the errno back to ni_tio_insn_config(). Signed-off-by:
-
H Hartley Sweeten authored
All the counter_dev->variant options are handled by the switch. Remove the BUG() which can never occur. Signed-off-by:
-
H Hartley Sweeten authored
The 'stale_data' pointer is always NULL. Just remove it. Signed-off-by:
-
