lightnvm: pblk: verify that cache read is still valid
When a read is directed to the cache, we risk that the lba has been updated during the time we made the L2P table lookup and the time we are actually reading form the cache. We intentionally not hold the L2P lock not to block other threads. While strict ordering is not a guarantee at this level (unless REQ_FLUSH has been previously issued), we have experience that some databases that have recently implemented direct I/O support, issue metadata reads very close to the writes, without issuing a fsync in the middle. An easy way to support them while they is to make an extra effort and check the L2P map right before reading the cache. Signed-off-by: Javier González <javier@cnexlabs.com> Signed-off-by: Matias Bjørling <matias@cnexlabs.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
This commit is contained in:

committed by
Jens Axboe

parent
b5e063a286
commit
076984669d
@@ -670,7 +670,7 @@ unsigned int pblk_rb_read_to_bio_list(struct pblk_rb *rb, struct bio *bio,
|
||||
struct list_head *list,
|
||||
unsigned int max);
|
||||
int pblk_rb_copy_to_bio(struct pblk_rb *rb, struct bio *bio, sector_t lba,
|
||||
u64 pos, int bio_iter);
|
||||
struct ppa_addr ppa, int bio_iter);
|
||||
unsigned int pblk_rb_read_commit(struct pblk_rb *rb, unsigned int entries);
|
||||
|
||||
unsigned int pblk_rb_sync_init(struct pblk_rb *rb, unsigned long *flags);
|
||||
@@ -1037,6 +1037,14 @@ static inline void pblk_ppa_set_empty(struct ppa_addr *ppa_addr)
|
||||
ppa_addr->ppa = ADDR_EMPTY;
|
||||
}
|
||||
|
||||
static inline bool pblk_ppa_comp(struct ppa_addr lppa, struct ppa_addr rppa)
|
||||
{
|
||||
if (lppa.ppa == rppa.ppa)
|
||||
return true;
|
||||
|
||||
return false;
|
||||
}
|
||||
|
||||
static inline int pblk_addr_in_cache(struct ppa_addr ppa)
|
||||
{
|
||||
return (ppa.ppa != ADDR_EMPTY && ppa.c.is_cached);
|
||||
|
Reference in New Issue
Block a user