文件列表:

.travis.yml (310, 2016-08-28)
eVSSIM (0, 2016-08-28)
eVSSIM\CONFIG (0, 2016-08-28)
eVSSIM\CONFIG\QEMU_MAKEFILE (0, 2016-08-28)
eVSSIM\CONFIG\QEMU_MAKEFILE\Makefile_pm (13072, 2016-08-28)
eVSSIM\CONFIG\Stats Comments (247, 2016-08-28)
eVSSIM\CONFIG\ssd.conf (346, 2016-08-28)
eVSSIM\CONFIG\vssim_config_manager.c (5257, 2016-08-28)
eVSSIM\CONFIG\vssim_config_manager.h (1792, 2016-08-28)
eVSSIM\FTL_SOURCE (0, 2016-08-28)
eVSSIM\FTL_SOURCE\COMMON (0, 2016-08-28)
eVSSIM\FTL_SOURCE\COMMON\common.h (4184, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP (0, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\TOOLS (0, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\TOOLS\uthash.h (61388, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl.c (8275, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl.h (749, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_gc_manager.c (6439, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_gc_manager.h (711, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_inverse_mapping_manager.c (19252, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_inverse_mapping_manager.h (2589, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_mapping_manager.c (5064, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_mapping_manager.h (955, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_obj_strategy.c (19135, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_obj_strategy.h (2809, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_sect_strategy.c (5982, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_sect_strategy.h (520, 2016-08-28)
eVSSIM\FTL_SOURCE\PAGE_MAP\ftl_type.h (182, 2016-08-28)
eVSSIM\FTL_SOURCE\PERF_MODULE (0, 2016-08-28)
eVSSIM\FTL_SOURCE\PERF_MODULE\ftl_perf_manager.c (9725, 2016-08-28)
eVSSIM\FTL_SOURCE\PERF_MODULE\ftl_perf_manager.h (1411, 2016-08-28)
eVSSIM\MONITOR (0, 2016-08-28)
eVSSIM\MONITOR\SSD_MONITOR_PM (0, 2016-08-28)
eVSSIM\MONITOR\SSD_MONITOR_PM\Makefile.new (3662, 2016-08-28)
eVSSIM\MONITOR\SSD_MONITOR_PM\Makefile.old (3436, 2016-08-28)
eVSSIM\MONITOR\SSD_MONITOR_PM\VssimStat (0, 2016-08-28)
... ...

[](https://travis-ci.org/florpor/simulator) #Developers Guide ##Sign In using GitHub credentials Follow the instructions at [Getting started with GerritHub](https://review.gerrithub.io/static/intro.html) 1. [Sign In](https://review.gerrithub.io/login) with your GitHub username and password. 2. Allow GerritHub accessing your profile 3. Select the SSH Public Keys you want to import ##Installing git-review We recommend using the git-review tool which is a git subcommand that handles all the details of working with Gerrit. On Ubuntu Precise (12.04) and later install it as any other package: ``` apt-get install git-review ``` On CentOS 6.5 and later install it by: ``` yum install git-review ``` ##Starting Work on a New Project Clone the [gerrit repository](https://review.gerrithub.io/#/admin/projects/davidsaOpenu/simulator) using ssh ##Starting a Change Once your local repository is set up as above, you must use the following workflow 1. cd 2. Make sure you have the latest upstream changes by *git pull* ##Committing a Change Make your changes, commit them, and submit them for review: ``` git commit -a ``` Commit messages should start with a short 50 character or less summary in a single paragraph. The following paragraph(s) should explain the change in more detail describing a propblem solved by the change and the way it was solved. For example: ``` Fixing ssd.conf parameters calculation based on disk size Reducing disk size was ac heaved by recalculating flash number. Which is wrong because this number can't drop too much. Block number should be recalculated based on desired disk size. ``` If your changes addresses a blueprint or a bug, be sure to mention them in the commit message using the following syntax: ``` Implements: blueprint BLUEPRINT Closes-Bug: ####### (Partial-Bug or Related-Bug are options) ``` ##Previewing a Change Before submitting your change, you should make sure that your change does not contain the files or lines you do not explicitly change: ``` git show ``` ##Submitting a Change for Review Once you have committed a change to your local repository, all you need to do to send it to Gerrit for code review is run: ``` git review ``` ##Updating a Change If the code review process suggests additional changes, make and amend the changes to the existing commit. Leave the existing Change-Id: footer in the commit message as-is. Gerrit knows that this is an updated patchset for an existing change: ``` git commit -a --amend git review ```

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：