Re: [PATCH 23/28] mbcache: make mbcache more generic
Tahsin Erdogan via Jfs-discussion <[email protected]>
| Newsgroups | gmane.comp.file-systems.jfs.general |
|---|---|
| Message-ID | <CAAeU0aMLrfhnhqzD9PH2UjHSrc64AC_85rAEz626jcuFjLXY2g__14320.5301756554$1497551127$gmane$org@mail.gmail.com> |
On Thu, Jun 15, 2017 at 12:41 AM, Jan Kara <[email protected]> wrote: > Can you explain a bit more what do you mean by "make it more generic" as it > seems you just rename a couple of things here... The change is really just that, having names that are more generic which do not limit use cases to block sharing. In a subsequent patch in the series ("[PATCH v4 27/28] ext4: xattr inode deduplication"), we start using the mbcache code to share xattr inodes. With that patch, old mb_cache_entry.e_block field could be holding either a block number or an inode number, so I renamed things to make them more generic. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot