>-----Original Message----- >From: Prakash Prasad [mailto:prakash_prasad@xxxxxxxxx] >Sent: Monday, October 21, 2013 9:59 AM >To: Lisa Nguyen; gregkh@xxxxxxxxxxxxxxxxxxx >Cc: devel@xxxxxxxxxxxxxxxxxxxx; Peng, Tao; andreas.dilger@xxxxxxxxx >Subject: Re: [PATCH 18/22] staging: lustre: Update struct variables in >lprocfs_status.c > >Can anyone please let me know where can I get the staging area drivers code >and their test cases? > Great to know that you are interested in testing Lustre kernel client. Firstly, you need to clone the out of tree Lustre code from git://git.whamcloud.com/fs/lustre-release.git. It contains necessary user space tools for both Lustre client and server. All the test cases in lustre/tests/ directory. You can build only the user space tools by `./configure --disable-server --disable-client --disable-modules --disable-liblustre`. To set up environment for testing, you need also a Lustre server environment to test against. Currently Lustre server only works for older version of kernels. Please follow the instructions on https://wiki.hpdd.intel.com/display/PUB/HPDD+Wiki+Front+Page especially below pages: 1. https://wiki.hpdd.intel.com/display/PUB/Getting+started+with+Lustre 2. https://wiki.hpdd.intel.com/display/PUB/Lustre+Support+Matrix 3. https://wiki.hpdd.intel.com/display/PUB/Building+Lustre+from+Source 4. https://wiki.hpdd.intel.com/display/PUB/Testing+a+Lustre+filesystem Please be patient on reading these docs and doing setup. Lustre is a complicated piece of software and it usually takes some time for starters to get hands on it. If you see any issues on environment setup, please send emails to hpdd-discuss@xxxxxxxxxxxx and lustre-discuss@xxxxxxxxxxxxxxxx. Lustre community people will be happy to help you out. Thanks, Tao >As I am beginner in this group - I understand that I need to download the >staging area device drivers code. In the source code tree there would be a >TODO file. Accordingly we have to fix and propagate it identifying the owner >also. > >But how are we suppose to test out the same - where are the test cases and >process to execute them? > >Regards, >Prakash > > >On Monday, 21 October 2013 4:28 AM, Lisa Nguyen <lisa@xxxxxxxxxxxxxxx> >wrote: > >Assuming the patch to update the structs in libcfs_hash header file has been >applied, this patch will update the struct variables in lprocfs_status.c to avoid >build errors. > >Signed-off-by: Lisa Nguyen <lisa@xxxxxxxxxxxxxxx> >--- >drivers/staging/lustre/lustre/obdclass/lprocfs_status.c | 6 +++--- >1 file changed, 3 insertions(+), 3 deletions(-) > >diff --git a/drivers/staging/lustre/lustre/obdclass/lprocfs_status.c >b/drivers/staging/lustre/lustre/obdclass/lprocfs_status.c >index a95f60a..4b2cb81 100644 >--- a/drivers/staging/lustre/lustre/obdclass/lprocfs_status.c >+++ b/drivers/staging/lustre/lustre/obdclass/lprocfs_status.c >@@ -898,7 +898,7 @@ static void lprocfs_free_client_stats(struct nid_stat >*client_stat) > >void lprocfs_free_per_client_stats(struct obd_device *obd) { >- cfs_hash_t *hash = obd->obd_nid_stats_hash; >+ struct cfs_hash *hash = obd->obd_nid_stats_hash; > struct nid_stat *stat; > > /* we need extra list - because hash_exit called to early */ @@ -1422,7 >+1422,7 @@ void lprocfs_init_ldlm_stats(struct lprocfs_stats *ldlm_stats) } >EXPORT_SYMBOL(lprocfs_init_ldlm_stats); > >-int lprocfs_exp_print_uuid(cfs_hash_t *hs, cfs_hash_bd_t *bd, >+int lprocfs_exp_print_uuid(struct cfs_hash *hs, struct cfs_hash_bd *bd, > struct hlist_node *hnode, void *data) > >{ >@@ -1453,7 +1453,7 @@ struct exp_hash_cb_data { > bool first; >}; > >-int lprocfs_exp_print_hash(cfs_hash_t *hs, cfs_hash_bd_t *bd, >+int lprocfs_exp_print_hash(struct cfs_hash *hs, struct cfs_hash_bd *bd, > struct hlist_node *hnode, void *cb_data) > >{ >-- >1.8.1.2 > >_______________________________________________ >devel mailing list >devel@xxxxxxxxxxxxxxxxxxxxxx >http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel > > _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
