[LU-8402] OBD_CONNECT_* flags retirement

Related — Mon, 25 Mar 2019 21:24:24 +0000

Several of the OBD_CONNECT_* flags have outlived their usefulness and should just always assume to be set or unset so that affected code paths can be simplified.

[10:23:19 AM] John Hammond: It seems like some of the OBD_CONNECT_* flags can be assumed to be set for all supported versions and then some. For example OBD_CONNECT_IBITS. Should we put together a list of such flags which can be required at connect time and then other code that check these flags can be simplified?
[10:31:36 AM] Andreas Dilger: I wouldn't be against that
[10:31:55 AM] John Hammond: OK, I'll open a ticket.
[10:35:55 AM] Andreas Dilger: there are two ways that could be handled... either require that it be set and refuse clients that don't have it, or assume that the flag is set at the server and then eventually stop sending it from the client and deprecate it completely
[10:38:25 AM] John Hammond: I was leaning towards the first. What do you suggest?
[11:26:15 AM] Andreas Dilger: I'd be inclined toward the second. I don't see much value to keeping around flags forever that will always be set.

Candidates for retirement include:

OBD_CONNECT_IBITS
OBD_CONNECT_ATTRFID
OBD_CONNECT_NODEVOH
OBD_CONNECT_CANCELSET
OBD_CONNECT_REAL
OBD_CONNECT_FID
OBD_CONNECT_VBR
OBD_CONNECT_LOV_V3
OBD_CONNECT_FULL20

There are probably others as well. Some archeology is needed to determine in which versions these flags were added or started to be ignored.

Whamcloud Community JIRA

[LU-8402] OBD_CONNECT_* flags retirement