Re: [dpdk-dev] [PATCH 2/2] cryptodev: change symmetric session structure

["Ananyev, Konstantin" <konstantin.ananyev@intel.com>]

Hi Fan,

> -
>  /** Cryptodev symmetric crypto session
>   * Each session is derived from a fixed xform chain. Therefore each session
>   * has a fixed algo, key, op-type, digest_len etc.
>   */
>  struct rte_cryptodev_sym_session {
> -	__extension__ void *sess_private_data[0];
> -	/**< Private symmetric session material */
> +	uint64_t userdata;
> +	/**< Can be used for external metadata */
> +	uint16_t nb_drivers;
> +	/**< number of elements in sess_data array */
> +	uint16_t priv_size;
> +	/**< session private data will be placed after sess_data */
> +	__extension__ struct {
> +		void *data;
> +		uint16_t refcnt;
> +	} sess_data[0];
> +	/**< Driver specific session material, variable size */
>  };
> 

As discussed in the thread [1] to avoid naming collisions, it was
agreed to re-name 'userdata' field to 'opaque_data' and
'priv_size' to ' 'user_data_sz'.
Konstantin

[1] https://mails.dpdk.org/archives/dev/2018-November/118941.html