[LU-10341] kkuc shoud send HALs only to suitable CTs Created: 07/Dec/17  Updated: 09/Feb/18  Resolved: 04/Jan/18

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: Lustre 2.11.0, Lustre 2.10.4

Type: Bug Priority: Minor
Reporter: John Hammond Assignee: John Hammond
Resolution: Fixed Votes: 0
Labels: hsm

Issue Links:
Related
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

When a client has multiple Lustre mounts and multiple copytools then using the current kkuc to delived HALs to CTs is inefficient since it broadcasts each HAL to all CT. This consumes kkuc pipe space and causes extra CT wakeups. So a UUID field to struct kkuc_reg to permit filtering HALs by the mount point UUID.



 Comments   
Comment by Gerrit Updater [ 07/Dec/17 ]

John L. Hammond (john.hammond@intel.com) uploaded a new patch: https://review.whamcloud.com/30419
Subject: LU-10341 hsm: filter kkuc write by client UUID
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 693f88ca9b4daf5f4af606b5444edc628e5a9108

Comment by Gerrit Updater [ 04/Jan/18 ]

Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/30419/
Subject: LU-10341 hsm: filter kkuc write by client UUID
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: c73736545fafac4373569187e064aab9cd435320

Comment by Peter Jones [ 04/Jan/18 ]

Landed for 2.11

Comment by Gerrit Updater [ 04/Jan/18 ]

Minh Diep (minh.diep@intel.com) uploaded a new patch: https://review.whamcloud.com/30719
Subject: LU-10341 hsm: filter kkuc write by client UUID
Project: fs/lustre-release
Branch: b2_10
Current Patch Set: 1
Commit: f0cbb1d615913a515ac1baa706c2baf34d459eff

Comment by Gerrit Updater [ 09/Feb/18 ]

John L. Hammond (john.hammond@intel.com) merged in patch https://review.whamcloud.com/30719/
Subject: LU-10341 hsm: filter kkuc write by client UUID
Project: fs/lustre-release
Branch: b2_10
Current Patch Set:
Commit: 10329bd6e9c8bb58ddf71cc1ce03d82bc6a731d8

Generated at Sat Feb 10 02:34:11 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.