On Wed, Jun 01, 2022 at 02:33:09PM +0800, D. Wythe wrote: > > 在 2022/5/25 下午9:42, Alexandra Winter 写道: > > > We need to carefully evaluate them and make sure everything is compatible > > with the existing implementations of SMC-D and SMC-R v1 and v2. In the > > typical s390 environment ROCE LAG is propably not good enough, as the card > > is still a single point of failure. So your ideas need to be compatible > > with link redundancy. We also need to consider that the extension of the > > protocol does not block other desirable extensions. > > > > Your prototype is very helpful for the understanding. Before submitting any > > code patches to net-next, we should agree on the details of the protocol > > extension. Maybe you could formulate your proposal in plain text, so we can > > discuss it here? > > > > We also need to inform you that several public holidays are upcoming in the > > next weeks and several of our team will be out for summer vacation, so please > > allow for longer response times. > > > > Kind regards > > Alexandra Winter > > > > Hi alls, > > In order to achieve signle-link compatibility, we must > complete at least once negotiation. We wish to provide > higher scalability while meeting this feature. There are > few ways to reach this. > > 1. Use the available reserved bits. According to > the SMC v2 protocol, there are at least 28 reserved octets > in PROPOSAL MESSAGE and at least 10 reserved octets in > ACCEPT MESSAGE are available. We can define an area in which > as a feature area, works like bitmap. Considering the subsequent > scalability, we MAY use at least 2 reserved ctets, which can support > negotiation of at least 16 features. > > 2. Unify all the areas named extension in current > SMC v2 protocol spec without reinterpreting any existing field > and field offset changes, including 'PROPOSAL V1 IP Subnet Extension', > 'PROPOSAL V2 Extension', 'PROPOSAL SMC-DV2 EXTENSION' .etc. And provides > the ability to grow dynamically as needs expand. This scheme will use > at least 10 reserved octets in the PROPOSAL MESSAGE and at least 4 reserved > octets in ACCEPT MESSAGE and CONFIRM MESSAGE. Fortunately, we only need to > use reserved fields, and the current reserved fields are sufficient. And > then we can easily add a new extension named SIGNLE LINK. Limited by space, > the details will be elaborated after the scheme is finalized. After reading this and latest version of protocol, I agree with that the idea to provide a more flexible extension facilities. And, it's a good chance for us to set here talking about the protocol extension. There are some potential scenarios that need flexible extensions in my mind: - other protocols support, such as iWARP / IB or new version protocol, - dozens of feature flags in the future, like this proposal. With the growth of new feature, it could overflow bitmap. Actually, this extension facilities are very similar to TCP options. So what about your opinions about the solution of this? If there are some existed approaches for the future extensions, maybe this can get involved in it. Or we can start a discuss about this as this mail mentioned. Also, I am wondering if there is plan to update the RFC7609, add the latest v2 support? Thanks, Tony Lu
