> Preloading of these caches is supported via a file which is > produced by OpenSM by the dump_pr plugin which contains > sufficient SA PathRecord information. Details on this > file format and configuring OpenSM for this are found in > dump_pr_notes.txt in dump_pr. > > File format is specified in ibacm_opts.cfg as follows: > path_rec_fnt full_opensm_v1 > > To preload these caches, ibacm service is started with -p option > which can also take optional path_rec_file which defaults to > ACM_CONF_DIR/ibacm_path_records.dump
I would rather use the config file versus adding command line parameters. This series will preload the cache, but it does not change the actual protocol ibacm uses for updates. I want to verify that this is your intent. I see within this patch that you override the address and route timeout values set by the user. I think the code should honor those settings. I wonder if it would make sense to treat file loading as a 'protocol' rather than a preload of the cache. By changing the timeout value, this is essentially what occurs. If the cached data can timeout, then there's an option for what ibacm should do. If it falls back to its configured address/route protocols, then this is truly a preload of the cache. An alternate option would be for ibacm to see if the input files had been updated, and if so, reload its cache. One drawback I see with using this as a simple preload mechanism is that the entire cache would timeout at once if cache timeouts are enabled. - Sean -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
