quoted

1. Why bcache refers to inodes ? The block driver layer does not have
an idea about the file system layed on top of it. (ext4). Is this
inode refers to device file? As per my
understanding the block layer gets bio_structure, it does not have a
notion of inodes...

You're probably looking at bcachefs, not bcache.

If you're interested in looking at bcache, it would be great if you can 
check out the most recent list issues and see if there is one you can work 
on: the "Re: BUG: drivers/md/bcache/writeback.c:237" thread, for example.

Also there are some places that could use a mempool.

It also occurs to me that we need a refactor around the cache 
functionality so it can take function pointers for per-cache-version 
cache volume operations.

-Eric

quoted

2. How the cache eviction work. ? for an example in processor caches
we evict the cache lines
within a set in a set associative cache using LRU/etc. How does
eviction happens in bcache/policy?

configurable: lru/fifo

quoted

3. Can i use any file system in backing device other than bcacheFS. ?
My abstract model on bcache says NO.

bcache, yes.  bcachefs, no (without loopback)

-Eric

quoted

I'm new to Linux driver programming. so I might be missing few trivial
details and hence the confusion..
appreciate if someone can shed some light on the above questions...

[1] bcache.evilpiepirate.org/BcacheGuide

thanks
Pradeep
--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html