Home
last modified time | relevance | path

Searched hist:"1 ac72433" (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/drivers/net/ethernet/qlogic/qed/
H A Dqed_int.h1ac72433 Thu Jun 01 07:29:07 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Remove assumption on SB order in IGU

Current code assumes there's a known layout for SBs in the IGU,
where all the SBs of a single entity would be laid in consecutive
order of vectors.

While the assumption is still kept by management firmware, we already
have the necessary information to eliminate it, so no reason to keep
it in code.

Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
1ac72433 Thu Jun 01 07:29:07 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Remove assumption on SB order in IGU

Current code assumes there's a known layout for SBs in the IGU,
where all the SBs of a single entity would be laid in consecutive
order of vectors.

While the assumption is still kept by management firmware, we already
have the necessary information to eliminate it, so no reason to keep
it in code.

Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
H A Dqed_int.c1ac72433 Thu Jun 01 07:29:07 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Remove assumption on SB order in IGU

Current code assumes there's a known layout for SBs in the IGU,
where all the SBs of a single entity would be laid in consecutive
order of vectors.

While the assumption is still kept by management firmware, we already
have the necessary information to eliminate it, so no reason to keep
it in code.

Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
1ac72433 Thu Jun 01 07:29:07 CDT 2017 Mintz, Yuval <Yuval.Mintz@cavium.com> qed: Remove assumption on SB order in IGU

Current code assumes there's a known layout for SBs in the IGU,
where all the SBs of a single entity would be laid in consecutive
order of vectors.

While the assumption is still kept by management firmware, we already
have the necessary information to eliminate it, so no reason to keep
it in code.

Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com>
Signed-off-by: David S. Miller <davem@davemloft.net>