UNIC: Support using MC GUID and table management

driver inclusion
category: feature
bugzilla: https://gitee.com/openeuler/kernel/issues/I850RQ


CVE: NA

-----------------------------------------------------

The MC guid is designed to send ub network control packets
to the peer end without knowing the peer guid. The packets
whose destination address is the MC guid can be sent to all
ports that support the MC guid. It is defined as 112-bit 1
and 16-bit protocol. Therefore, the valid data of the MC guid
is the last 16 bits. If the peer end supports an MC guid, it
indicates that the packets of the corresponding protocol
can be processed.

The driver implements a new .set_rx_mode for the ub to reuse
the ip maddr adding and deleting interfaces. Because the
original interface supports only an 8-byte address, only
the lower 64 bits of the mc guid can be configured. In addition,
the upper 48 bits of the 64 bits must be 1.

In terms of hardware entry management, hardware entries are
limited and one entry can be shared by multiple functions.
Therefore, entries are managed by checking whether the entry
exists before being added. In addition, promiscuous entries
are enabled when the number of entries is full. In addition,
for security purposes, hardware entries cannot be configured
for virtual functions.

Signed-off-by: Junxin Chen <chenjunxin1@huawei.com>
Signed-off-by: Haibin Lu <luhaibin10@hisilicon.com>