- 15 Aug, 2016 40 commits
-
-
Daeseok Youn authored
The 'ch_intr_tx' variable was used only for increasing. So the 'ch_intr_tx' variable is not useful for this driver. Signed-off-by:
Daeseok Youn <daeseok.youn@gmail.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Daeseok Youn authored
The 'ch_intr_modem' variable was used only for increasing. So the 'ch_intr_modem' variable is not useful for this driver. Signed-off-by:
-
Daeseok Youn authored
The 'intr_rx' variable was used only for increasing. So the 'intr_rx' variable is not useful for this driver. Signed-off-by:
-
Daeseok Youn authored
The 'intr_tx' variable was used only for increasing. So the 'intr_tx' variable is not useful for this driver. Signed-off-by:
-
Daeseok Youn authored
The 'intr_modem' variable was used only for increasing. So the 'intr_modem' variable is not useful for this driver. Signed-off-by:
-
Daeseok Youn authored
the "brd" was already checked for NULL before calling dgnc_do_remap(). the dgnc_do_remap() function was called only from the dgnc_found_board() and the DGNC_BOARD_MAGIC value was assigned to "brd->magic" in dgcn_found_board(). So it doesn't need to check about magic value. Signed-off-by:
-
Daeseok Youn authored
The 'intr_count' variable was used only for increasing. So the 'intr_count' variable is not useful for this driver. Signed-off-by:
-
Daeseok Youn authored
the "brd" value cannot be NULL in dgnc_finalize_board_init(). Because "brd" as a parameter of this function was already checked for NULL. the dgnc_finalize_board_init() as a static function was called only from dgnc_found_board() function and brd->magic value was assigned once in dgnc_found_board(). So it doesn't need to check for DGNC_BOARD_MAGIC value. Signed-off-by:
-
Daeseok Youn authored
Re-arrange the functions for removing forward declarations in dgnc_cls.c file. Signed-off-by:
-
Daeseok Youn authored
The dgnc_set_modem_info() used only channel_t variable. Any other variables were used only for checking NULL. So fist parameter changed from "tty_struct" to "channel_t" and useless NULL checks and variables are removed. Signed-off-by:
-
Daeseok Youn authored
The unit struct(un_t) was not used in dgnc_tty_hangup(). Signed-off-by:
-
Daeseok Youn authored
The local variable "bd" was not used in dgnc_carrier() function. Signed-off-by:
-
Daeseok Youn authored
The "result" variable in dgnc_get_mstat() was initialized with "-EIO". But if the "ch" is not null, "result" will be set to zero and if the "ch" is null, dgnc_get_mstat() will return "-ENXIO" as an error. So "-EIO" error value was useless in dgnc_get_mstat(). Signed-off-by:
-
Daeseok Youn authored
The dgnc_block_til_ready() is only used in dgnc_tty_open(). The unit data(struct un_t) was stored into tty->driver_data in dgnc_tty_open(). And also tty and un were tested about NULL so these variables doesn't need to check for NULL in dgnc_block_til_ready(). Signed-off-by:
-
Joshua Houghton authored
Add the __exit macro to the dgnc_cleanup_module(void) function in dgnc_driver.c Signed-off-by:
Joshua Houghton <josh@awful.name> Signed-off-by:
-
Al Viro authored
Signed-off-by:
Al Viro <viro@zeniv.linux.org.uk> Signed-off-by:
-
Al Viro authored
... by using ITER_BVEC recvmsg Signed-off-by:
-
Al Viro authored
Signed-off-by:
-
wang di authored
Increase the post-work for the statahead thread in the readdir case since it can become very busy. Signed-off-by:
wang di <di.wang@intel.com> Reviewed-on: http://review.whamcloud.com/10761 Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4906Reviewed-by:
John L. Hammond <john.hammond@intel.com> Reviewed-by:
Andreas Dilger <andreas.dilger@intel.com> Reviewed-by:
Oleg Drokin <oleg.drokin@intel.com> Signed-off-by:
James Simmons <jsimmons@infradead.org> Signed-off-by:
-
wang di authored
Some cases we want to preserve the ctx->pos value or use a different value altogther. So allow the passing in of a position offset to ll_dir_read. Signed-off-by:
-
wang di authored
We have if (1) conditionals which is pointless so remove it and the next code block is never called so remove that as well. Signed-off-by:
Jinshan Xiong <jinshan.xiong@intel.com> Reviewed-by:
-
wang di authored
Make some of the error reporting more clear for the statahead thread startup and is_first_dirent() function. Signed-off-by:
-
wang di authored
The variables api32 and hash64 was renamed to is_api32 and is_hash64. Signed-off-by:
-
wang di authored
Change the done flag from integer to bool. Signed-off-by:
-
wang di authored
Invert the done flag test to reduce the code indentation. If done is true release the page and break out of the while loop. Signed-off-by:
-
wang di authored
The variable next needs only to be set when done is false. Signed-off-by:
-
wang di authored
Instead of making a large chunk of code conditional based on if a page is valid we reverse the page validity test and exit the loop if the page is invalid instead. This allows a section of code to reduce its indentation one level. Signed-off-by:
-
wang di authored
Remove debug message and struct ll_inode_info. Signed-off-by:
-
wang di authored
Add struct md_op_data as a parameter to ll_dir_read. Signed-off-by:
-
wang di authored
We report the inode size but never print in the debug message that the number reported is the size. Signed-off-by:
-
wang di authored
The readdir operations lock was incomplete. This patch fills in the missing pieces. Signed-off-by:
-
wang di authored
Newer lustre version on metadata servers support different version of lmv magic. This add the new data structures to handle these new lmv magic versions. Signed-off-by:
-
wang di authored
Cache directory striping information that the clients receive from the metadata servers. Signed-off-by:
-
wang di authored
Remove the wiretest check for this data structure. Signed-off-by:
-
wang di authored
Rename struct lmv_stripe_md in struct lustre_md from mea to lmv. Signed-off-by:
-
wang di authored
Add new flags for metadata handling. These flags are related to DNE2 handling. Signed-off-by:
-
James Simmons authored
Port the xattr functionality to the new xattr_handler API. This is smallest changes needed to move to this new API. The function ll_removexattr can be replaced by generic_removexattr as well since it also uses the xattr_handler set xattr backend. To tell the difference between the two cases we test the flag passed in for XATTR_REPLACE. The ll_getxattr function is replaced by the generic_getxattr function. Signed-off-by:
-
Ben Evans authored
These #if 0 blocks have been in place for years. Assume they are not used and remove them Signed-off-by:
Ben Evans <bevans@cray.com> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8058 Reviewed-on: http://review.whamcloud.com/20414Reviewed-by:
James Simmons <uja.ornl@yahoo.com> Reviewed-by:
-
James Simmons authored
Split the function ll_getxattr_common into two functions. The code used for listing xattrs and ll_getxattr_common is placed into a new function ll_getxattr_list. This allows ll_listxattr to call directly ll_getxattr_list instead of going through ll_getxattr_common. This change is needed for the upcoming VFS move xattr_handler from [s|g]etxattr. Signed-off-by:
-
Bhaktipriya Shridhar authored
The workqueue is being used to run deferred work for the android binder. The "binder_deferred_workqueue" queues only a single work item and hence does not require ordering. Also, this workqueue is not being used on a memory recliam path. Hence, the singlethreaded workqueue has been replaced with the use of system_wq. System workqueues have been able to handle high level of concurrency for a long time now and hence it's not required to have a singlethreaded workqueue just to gain concurrency. Unlike a dedicated per-cpu workqueue created with create_singlethread_workqueue(), system_wq allows multiple work items to overlap executions even on the same CPU; however, a per-cpu workqueue doesn't have any CPU locality or global ordering guarantee unless the target CPU is explicitly specified and thus the increase of local concurrency shouldn't make any difference. Signed-off-by:
Bhaktipriya Shridhar <bhaktipriya96@gmail.com> Signed-off-by:
-
