path: root/xlators
diff options
authorSoumya Koduri <>2016-02-08 22:33:56 +0530
committerKaleb KEITHLEY <>2016-02-27 11:04:25 -0800
commit6f12a5767f6912f6913cd9dfa4c6a5484a766000 (patch)
tree5653e2e98177452d22c7554aa6d7956ec58a4192 /xlators
parent30e883d49475c5a99abdb4745e708bb1f9e25144 (diff)
gfapi: Use inode_forget in case of handle objects
Currently with gfapi, even if applications release their reference on paritular inode entries, those entries never get destroyed as they shall always have positive nlookup count unless inode_table exceeds lru limit. Since inodes and their contexts can consume considerable amount of memory, applications may end up consuming lot of memory and may even get OOM killed. To avoid that, have considered below approaches (for handle based access)- a) Do 'inode_lookup' only if the corresponding inode is created for the first time and forget it during close of the handle This shall not work as multiple handle objects can refer to same inode entry and inode_forget from second handle object onwards shall result in assert. b) Do 'inode_lookup' during a handle or fd creation But this approach shall affect the performance of the fops which operate on neither handle nor fd. c) current approach taken- Applications using glfs handle objects hold a reference on corresponding inode entries. Hence it is safe to forget those inodes and make nlookup count to '0' while trying to delete those handle objects. That way the last unref (i.e, from the last handle close) shall result in inode_destroy(). This is backport of the below patch - Change-Id: Id2c7ab178894a10c0030c143ba71e7813df8d18c Signed-off-by: Soumya Koduri <> BUG: 1311441 Reviewed-on: Reviewed-by: jiffin tony Thottan <> Reviewed-by: Niels de Vos <> Reviewed-by: Kaleb KEITHLEY <> Reviewed-on: Smoke: Gluster Build System <> NetBSD-regression: NetBSD Build System <> CentOS-regression: Gluster Build System <>
Diffstat (limited to 'xlators')
0 files changed, 0 insertions, 0 deletions