Searched refs:writepos (Results 1 - 2 of 2) sorted by relevance
| /linux-4.1.27/drivers/mtd/ |
| H A D | mtdswap.c | 669 loff_t writepos; mtdswap_write_block() local
691 writepos = (loff_t)*bp << PAGE_SHIFT; mtdswap_write_block()
692 ret = mtd_write(mtd, writepos, PAGE_SIZE, &retlen, buf); mtdswap_write_block()
|
| /linux-4.1.27/drivers/md/ |
| H A D | raid5.c | 5347 sector_t writepos, readpos, safepos; reshape_request() local
5385 writepos = conf->reshape_progress; reshape_request()
5386 sector_div(writepos, new_data_disks); reshape_request()
5392 writepos -= min_t(sector_t, reshape_sectors, writepos); reshape_request()
5396 writepos += reshape_sectors; reshape_request()
5401 /* Having calculated the 'writepos' possibly use it reshape_request()
5406 stripe_addr = writepos; reshape_request()
5412 BUG_ON(writepos != sector_nr + reshape_sectors); reshape_request()
5416 /* 'writepos' is the most advanced device address we might write. reshape_request()
5422 * increasing writepos if diff is positive. reshape_request()
5423 * If 'readpos' is then behind 'writepos', there is no way that we can reshape_request()
5427 * Otherwise if 'safepos' is behind 'writepos', then we really need to reshape_request()
5430 * So we insist on updating metadata if safepos is behind writepos and reshape_request()
5431 * readpos is beyond writepos. reshape_request()
5440 writepos += conf->min_offset_diff; reshape_request()
5443 ? (safepos > writepos && readpos < writepos) reshape_request()
5444 : (safepos < writepos && readpos > writepos)) || reshape_request()
|
Completed in 159 milliseconds