[LU-4585] remove OBJECT_UPDATE_PER_RPC_MAX Created: 05/Feb/14  Updated: 18/Jun/14  Resolved: 27/Mar/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.6.0
Fix Version/s: Lustre 2.6.0

Type: Improvement Priority: Critical
Reporter: Alex Zhuravlev Assignee: Di Wang
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
is duplicated by LU-4828 conf-sanity test_32a: (class_obd.c:73... Closed
Rank (Obsolete): 12532

 Description   

OBJECT_UPDATE_PER_RPC_MAX is a internal to OUT's implementation limit. OUT can use RPC directly instead of copying arguments into env. OUT just needs to maintain resizable array of object pointers.
probably in the same patch we could introduce a way to negotiate max.update buffer between the peers.

 Comments   
Comment by Andreas Dilger [ 10/Mar/14 ]

This should be fixed in 2.6 so that we don't get into problems with the protocol in later versions.

Comment by Di Wang [ 12/Mar/14 ]

http://review.whamcloud.com/9590

Comment by Jodi Levi (Inactive) [ 26/Mar/14 ]

Patch landed to Master. Please reopen ticket if more work is needed.

Comment by Di Wang [ 27/Mar/14 ]

reopen the ticket, since this will cause the memory leak.

Comment by Di Wang [ 27/Mar/14 ]

http://review.whamcloud.com/9804

Comment by Jodi Levi (Inactive) [ 27/Mar/14 ]

Patch landed to Master. Please reopen if more work is needed.

Generated at Sat Feb 10 01:44:03 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.