{"push_id":1747222730,"size":5,"distinct_size":5,"ref":"refs/heads/b_neo_stable_2.x","head":"63cf2877b9f178c90f3ed7089f0dd5e26dd0f0c9","before":"85040b15bd80e15f264333507b2645126646932c","commits":[{"sha":"a958ce8f123f42520ec8ea25b777281daa5976ad","author":{"name":"Andrew Perepechko","email":"e2878cd29bdffa86c5d49c1d4413e344197b0c0d@seagate.com"},"message":"MRP-4324 mdc: excessive memory consumption by the xattr cache\n\nThe refill operation of the xattr cache does not know the\nreply size in advance, so it makes a guess based on\nthe maxeasize value returned by the MDS.\n\nIn practice, it allocates 16 KiB for the common case and\n4 MiB for the large xattr case. However, a typical reply\nis just a few hundred bytes. Even worse, RHEL6 has a very\nbad vmalloc()/vfree() design with global locks.\n\nIf we follow the conservative approach, we can prepare a\nsingle memory page for the reply. It is large enough for\nany reasonable xattr set and, at the same time, it does\nnot require multiple page memory reclaim, which can be\ncostly.\n\nIf, for a specific file, the reply is larger than a single\npage, ptlrpc is prepared to handle that and will allocate\na larger buffer. Indeed, if this happens often and xattrs\nare often used to store large values, it makes sense to\ndisable the xattr cache at all since it wasn't designed for\nsuch [mis]use.\n\nChange-Id: I5f1ec73892cf8e8260a2558a1eb9a0d55e6eba96\nSigned-off-by: Andrew Perepechko <andrew.perepechko@seagate.com>\nReviewed-on: http://es-gerrit.xyus.xyratex.com:8080/15321\nReviewed-by: Alexandr Boyko <alexander.boyko@seagate.com>\nReviewed-by: Andriy Skulysh <andriy.skulysh@seagate.com>\nTested-by: Elena V. Gryaznova <elena.gryaznova@seagate.com>","distinct":true,"url":"https://api.github.com/repos/Xyratex/lustre-stable/commits/a958ce8f123f42520ec8ea25b777281daa5976ad"},{"sha":"feb55edc38bf7856b3ddf5fed85d2ec4a2912731","author":{"name":"Vitaly Fertman","email":"828f340a980752fca48c9632fb6fe65354f58a51@seagate.com"},"message":"Revert \"MRP-3532 ldlm: lost BL AST during failover\"\n\nThis reverts commit d5efd21a9f93ebfbb58cc8c309b50323b12c716a.","distinct":true,"url":"https://api.github.com/repos/Xyratex/lustre-stable/commits/feb55edc38bf7856b3ddf5fed85d2ec4a2912731"},{"sha":"4e832cad4a45b848f73cb4db347c8fd3687bfbae","author":{"name":"Niu Yawei","email":"bcf48b03afc4cf68b5dac35c9035a92e55e95075@intel.com"},"message":"LU-8306 ldlm: send blocking ASTs after lock replay\n\nIf blocking AST wasn't received by client before recovery,\nwe need to scan the whole waiting lock list to send blocking\nASTs after lock replay done, otherwise, client could be\nevicted unpurposely like following:\n\n- cl1 has a granted lock;\n- cl2 has a waiting lock, BL AST is sent but lost on a way;\n- failover, locks are replayed and applied on the server in\n  the correct order;\n- waiting lock is just put to the resource, no new BL AST\n  is re-sent, no timeout can happen for the granted lock on\n  server, no timeout for the waiting lock on client;\n- cl2 will be hanging for a long time until cl1 will cancel\n  its aged lock; may lead to cl2 eviction.\n\nSigned-off-by: Niu Yawei <yawei.niu@intel.com>\nChange-Id: I2a3fecf3b7fa79f96874d5ae21c599725334d9a5\nReviewed-on: https://review.whamcloud.com/24716\nReviewed-by: Vitaly Fertman <vitaly.fertman@seagate.com>\nTested-by: Jenkins\nTested-by: Maloo <hpdd-maloo@intel.com>\nReviewed-by: Oleg Drokin <oleg.drokin@intel.com>\nReviewed-by: Mike Pershin <mike.pershin@intel.com>","distinct":true,"url":"https://api.github.com/repos/Xyratex/lustre-stable/commits/4e832cad4a45b848f73cb4db347c8fd3687bfbae"},{"sha":"5ff00ca07d4423554c5d020ab97923774c9d84be","author":{"name":"Niu Yawei","email":"bcf48b03afc4cf68b5dac35c9035a92e55e95075@intel.com"},"message":"LU-8197 ptlrpc: set correct rq_timeout for normal replay reply\n\nFix from f3ce48ce543791d60326777d95ab2c9c03826965 introduced a\nregression which set larger rq_timeout of normal replay reply\nmistakenly, that result in incorrect estimated service time\nincrease during recovery.\n\nSigned-off-by: Niu Yawei <yawei.niu@intel.com>\nChange-Id: If62c94f6147e6d6d9ae5954e4847725e9cd66a67\nReviewed-on: https://review.whamcloud.com/23833\nTested-by: Jenkins\nReviewed-by: Lai Siyao <lai.siyao@intel.com>\nReviewed-by: Hongchao Zhang <hongchao.zhang@intel.com>\nTested-by: Maloo <hpdd-maloo@intel.com>\nReviewed-by: Oleg Drokin <oleg.drokin@intel.com>","distinct":true,"url":"https://api.github.com/repos/Xyratex/lustre-stable/commits/5ff00ca07d4423554c5d020ab97923774c9d84be"},{"sha":"63cf2877b9f178c90f3ed7089f0dd5e26dd0f0c9","author":{"name":"James Nunez","email":"5115fbf49bd5f8f94048f7a13b521ad8f73f80b9@intel.com"},"message":"LU-8366 test: Remove PIOS tests\n\nPIOS is an old benchmark and is not open source. PIOS should\nbe removed from sanity-benchmark.\n\nTest-Parameters: trivial testlist=sanity-benchmark\nSigned-off-by: James Nunez <james.a.nunez@intel.com>\nChange-Id: Id89ab1107e4d7e444f6149d04bd90b4ea8c7828b\nReviewed-on: https://review.whamcloud.com/26014\nReviewed-by: Andreas Dilger <andreas.dilger@intel.com>\nTested-by: Jenkins\nTested-by: Maloo <hpdd-maloo@intel.com>\nReviewed-by: Cliff White <cliff.white@intel.com>","distinct":true,"url":"https://api.github.com/repos/Xyratex/lustre-stable/commits/63cf2877b9f178c90f3ed7089f0dd5e26dd0f0c9"}]}
{"actor":{"display_login":"MorpheusTeam"}}