> Tx-timeout mostly happens due to some issue in the device. In such cases,
> debug dump would be helpful for identifying the cause of the issue.
> This patch adds support to spill debug data during the Tx timeout. Here
> bnx2x_panic_dump() API is used instead of bnx2x_panic(), since we still
> wan
uot;control_action": {
Relocate the open/close of the JSON object to declare the object only
for the case that needs it.
Signed-off-by: Yuval Mintz
---
tc/m_action.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/tc/m_action.c b/tc/m_action.c
index 2f85d35..8993b93 1
On Mon, Mar 26, 2018 at 03:13:47AM -0700, Sudarsana Reddy Kalluru wrote:
> This patch adds the required driver support for updating the flash or
> non volatile memory of the adapter. At highlevel, flash upgrade comprises
> of reading the flash images from the input file, validating the images and
>
On Mon, Mar 26, 2018 at 03:13:45AM -0700, Sudarsana Reddy Kalluru wrote:
> This patch add support for populating the flash image attributes.
s/add/adds/
[...]
> -int qed_mcp_bist_nvm_test_get_image_att(struct qed_hwfn *p_hwfn,
> - struct qed_ptt *p_ptt,
> -
> >>> After unshare test kworker hangs for ages:
> >>>
> >>> $ while :; do unshare -n true; done &
> >>>
> >>> $ perf report
> >>> - 88,82% 0,00% kworker/u16:0 [kernel.vmlinux] [k]
> >>> cleanup_net
> >>> cleanup_net
> >>> - ops_exit_list.isra.9
> >>>
> - /* Free Task CXT */
> + /* Free Task CXT ( Intentionally RoCE as task-id is shared between
> + * RoCE and iWARP
> + */
Broken parenthesis In comment...
Now that both ipmr and ip6mr are using the same mr_table structure,
we can have a common function to allocate & initialize a new instance.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute_base.h | 17 +
net/ipv4/ipmr.c
With the exception of the final dump, ipmr and ip6mr have the exact same
seq logic for traversing a given mr_table. Refactor that code and make
it common.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute_base.h | 69
net/ipv4
]
RFC -> v1:
- Corrected support for CONFIG_IP{,V6}_MROUTE_MULTIPLE_TABLES
- Addressed a couple of kbuild test robot issues
Yuval Mintz (11):
ipmr,ipmr6: Define a uniform vif_device
ip6mr: Make mroute_sk rcu-based
ip6mr: Align hash implementation to ipmr
mroute*: Make mr_table a com
] mr_mfc has to be the first
field inside every multicast routing abstraction utilizing it.
Signed-off-by: Yuval Mintz
---
drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c | 21 +-
include/linux/mroute.h| 45 +---
include/linux/mroute6.h | 23
e
distinct suffix.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute.h | 21
include/linux/mroute6.h | 1 -
include/linux/mroute_base.h | 46 +++
include/net/netns/ipv6.h| 2 +-
net/ipv4/ipmr.c | 2 -
net/ipv6/ip6mr.c
Since commit 8fb472c09b9d ("ipmr: improve hash scalability") ipmr has
been using rhashtable as a basis for its mfc routes, but ip6mr is
currently still using the old private MFC hash implementation.
Align ip6mr to the current ipmr implementation.
Signed-off-by: Yuval Mintz
Acked-b
ed by ipmr.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute.h | 9 -
include/linux/mroute6.h | 3 ---
include/linux/mroute_base.h | 9 +
net/ipv6/ip6mr.c| 3 ---
4 files changed, 9 insertions(+), 15 deletions(-)
diff --git
Same as previously done with the mfc seq, the logic for the vif seq is
refactored to be shared between ipmr and ip6mr.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute_base.h | 33 ++
net/ipv4/ipmr.c | 49
common
flows, in this case - the hash parameters and a comparison key
representing a (*,*) route.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 52 +--
net/ipv4/ipmr.c | 71 ++-
net/ipv4/ipmr_base.c
In ipmr the mr_table socket is handled under RCU. Introduce the same
for ip6mr.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute6.h | 6 +++---
net/ipv6/ip6_output.c | 2 +-
net/ipv6/ip6mr.c| 45 +++--
3 files
vif_device fields in a new common source file. This requires modifying
the ipv{4,6] Kconfig and ipv4 makefile as we're introducing a new common
config option - CONFIG_IP_MROUTE_COMMON.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute.h
between the two.
Notice this requires creating an mr_table iterator for each, as the
for-each preprocessor macro can't be used by the common logic.
Signed-off-by: Yuval Mintz
Acked-by: Nikolay Aleksandrov
---
include/linux/mroute_base.h | 29
net/ipv4/ipmr.c
On Wed, Feb 28, 2018 at 12:38:20AM +0200, Nikolay Aleksandrov wrote:
> On 27/02/18 20:58, Yuval Mintz wrote:
> > mfc_cache and mfc6_cache are almost identical - the main difference is
> > in the origin/group addresses and comparison-key. Make a common
> > structure enca
> >> > If so, for how long? They should certainly be removed eventually. How
> >> > do we ensure we don't forget?
> >> >
> >> > Seems to me it would be better to remove them right now.
> >>
> >> I can do that unless someone objects.
> >
> >I don't object, but FWIW keep in mind extack errors don't s
e
distinct suffix.
Signed-off-by: Yuval Mintz
---
include/linux/mroute.h | 21
include/linux/mroute6.h | 1 -
include/linux/mroute_base.h | 46 +++
include/net/netns/ipv6.h| 2 +-
net/ipv4/ipmr.c | 2 -
net/ipv6/ip6mr.c
] mr_mfc has to be the first
field inside every multicast routing abstraction utilizing it.
Signed-off-by: Yuval Mintz
---
drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c | 21 +-
include/linux/mroute.h| 45 +---
include/linux/mroute6.h | 23
ed by ipmr.
Signed-off-by: Yuval Mintz
---
include/linux/mroute.h | 9 -
include/linux/mroute6.h | 3 ---
include/linux/mroute_base.h | 9 +
net/ipv6/ip6mr.c| 3 ---
4 files changed, 9 insertions(+), 15 deletions(-)
diff --git a/include/linux/mroute.h b/inc
between the two.
Notice this requires creating an mr_table iterator for each, as the
for-each preprocessor macro can't be used by the common logic.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 29
net/ipv4/ipmr.c
Since commit 8fb472c09b9d ("ipmr: improve hash scalability") ipmr has
been using rhashtable as a basis for its mfc routes, but ip6mr is
currently still using the old private MFC hash implementation.
Align ip6mr to the current ipmr implementation.
Signed-off-by: Yuval Mintz
---
inc
With the exception of the final dump, ipmr and ip6mr have the exact same
seq logic for traversing a given mr_table. Refactor that code and make
it common.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 69
net/ipv4/ipmr.c | 93
common
flows, in this case - the hash parameters and a comparison key
representing a (*,*) route.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 52 +--
net/ipv4/ipmr.c | 71 ++-
net/ipv4/ipmr_base.c
In ipmr the mr_table socket is handled under RCU. Introduce the same
for ip6mr.
Signed-off-by: Yuval Mintz
---
include/linux/mroute6.h | 6 +++---
net/ipv6/ip6_output.c | 2 +-
net/ipv6/ip6mr.c| 45 +++--
3 files changed, 31 insertions(+), 22
Same as previously done with the mfc seq, the logic for the vif seq is
refactored to be shared between ipmr and ip6mr.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 33 ++
net/ipv4/ipmr.c | 49
vif_device fields in a new common source file. This requires modifying
the ipv{4,6] Kconfig and ipv4 makefile as we're introducing a new common
config option - CONFIG_IP_MROUTE_COMMON.
Signed-off-by: Yuval Mintz
---
include/linux/mroute.h | 13 +---
include/linux/mroute6.h
Now that both ipmr and ip6mr are using the same mr_table structure,
we can have a common function to allocate & initialize a new instance.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 17 +
net/ipv4/ipmr.c | 27 ++-
net/
bot issues
Yuval Mintz (11):
ipmr,ipmr6: Define a uniform vif_device
ip6mr: Make mroute_sk rcu-based
ip6mr: Align hash implementation to ipmr
mroute*: Make mr_table a common struct
ipmr, ip6mr: Unite creation of new mr_table
ipmr, ip6mr: Make mfc_cache a common structure
ipmr, ip6mr: Un
Since commit 8fb472c09b9d ("ipmr: improve hash scalability") ipmr has
been using rhashtable as a basis for its mfc routes, but ip6mr is
currently still using the old private MFC hash implementation.
Align ip6mr to the current ipmr implementation.
Signed-off-by: Yuval Mintz
---
inc
Same as previously done with the mfc seq, the logic for the vif seq is
refactored to be shared between ipmr and ip6mr.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 33 ++
net/ipv4/ipmr.c | 49
] mr_mfc has to be the first
field inside every multicast routing abstraction utilizing it.
Signed-off-by: Yuval Mintz
---
drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c | 21 +-
include/linux/mroute.h| 45 +---
include/linux/mroute6.h | 23
offloading as well, as almost all structures
related to the offloading would be shared between the two protocols.
Yuval Mintz (11):
ipmr,ipmr6: Define a uniform vif_device
ip6mr: Make mroute_sk rcu-based
ip6mr: Align hash implementation to ipmr
mroute*: Make mr_table a common struct
ipmr
between the two.
Notice this requires creating an mr_table iterator for each, as the
for-each preprocessor macro can't be used by the common logic.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 29 +
net/ipv4/ipmr.c
e
distinct suffix.
Signed-off-by: Yuval Mintz
---
include/linux/mroute.h | 21 ---
include/linux/mroute6.h | 1 -
include/linux/mroute_base.h | 46 +++
include/net/netns/ipv6.h| 2 +-
net/ipv4/ipmr.c | 2 -
net/ipv6/ip6mr.c
Now that both ipmr and ip6mr are using the same mr_table structure,
we can have a common function to allocate & initialize a new instance.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 17 +
net/ipv4/ipmr.c | 27 ++-
net/
ed by ipmr.
Signed-off-by: Yuval Mintz
---
include/linux/mroute.h | 9 -
include/linux/mroute6.h | 3 ---
include/linux/mroute_base.h | 9 +
net/ipv6/ip6mr.c| 3 ---
4 files changed, 9 insertions(+), 15 deletions(-)
diff --git a/include/linux/mroute.h b/inc
With the exception of the final dump, ipmr and ip6mr have the exact same
seq logic for traversing a given mr_table. Refactor that code and make
it common.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 69
net/ipv4/ipmr.c | 93
In ipmr the mr_table socket is handled under RCU. Introduce the same
for ip6mr.
Signed-off-by: Yuval Mintz
---
include/linux/mroute6.h | 6 +++---
net/ipv6/ip6_output.c | 2 +-
net/ipv6/ip6mr.c| 43 ++-
3 files changed, 30 insertions(+), 21
vif_device fields in a new common source file. This requires modifying
the ipv{4,6] Kconfig and ipv4 makefile as we're introducing a new common
config option - CONFIG_IP_MROUTE_COMMON.
Signed-off-by: Yuval Mintz
---
include/linux/mroute.h | 13 +---
include/linux/mroute6.h
common
flows, in this case - the hash parameters and a comparison key
representing a (*,*) route.
Signed-off-by: Yuval Mintz
---
include/linux/mroute_base.h | 52 +--
net/ipv4/ipmr.c | 71 ++-
net/ipv4/ipmr_base.c
> > > Hm. You you need this just because you didn't add the backlog
> > > pointer to destroy? AFAIK on destroy we are free to reset stats as
> > > well, thus simplifying your driver... Let me know if I
> > > misunderstand.
> >
> > This is meant exactly for the scenario where qdisc didn't get
> >
se of a qdisc that stops being offloaded but is not destroyed, backlog
> > value needs to be updated about the un-offloading.
> > For that reason an unoffload function is being added to the ops struct.
> >
> > Signed-off-by: Nogah Frankel
> > Reviewed-by: Yuval Mintz
> > > > +struct tc_prio_qopt_offload_params {
> > > > + int bands;
> > > > + u8 priomap[TC_PRIO_MAX + 1];
> > > > + /* In case that a prio qdisc is offloaded and now is changed to
> > > > a
> > > > +* non-offloadedable config, it needs to update the backlog
> > > > value
> > +struct tc_prio_qopt_offload_params {
> > + int bands;
> > + u8 priomap[TC_PRIO_MAX + 1];
> > + /* In case that a prio qdisc is offloaded and now is changed to a
> > +* non-offloadedable config, it needs to update the backlog value
> > +* to negate the HW backlog value.
> > +*
> >>> Many of the ASIC's internal resources are limited and are shared
> between
> >>> several hardware procedures. For example, unified hash-based memory
> can
> >>> be used for many lookup purposes, like FDB and LPM. In many cases the
> user
> >>> can provide a partitioning scheme for such a reso
> Many of the ASIC's internal resources are limited and are shared
> between
> several hardware procedures. For example, unified hash-based memory
> can
> be used for many lookup purposes, like FDB and LPM. In many cases the
> user
> can provide a partitioning scheme for such a
> >> Many of the ASIC's internal resources are limited and are shared between
> >> several hardware procedures. For example, unified hash-based memory
> can
> >> be used for many lookup purposes, like FDB and LPM. In many cases the
> user
> >> can provide a partitioning scheme for such a resource i
> >Use the newly added TCA_HW_OFFLOAD indication from kernel
> >to print a consistent 'offloaded' message to user when listing qdiscs.
> >
> >Signed-off-by: Yuval Mintz
>
> Reviewed-by: Jiri Pirko
Just now saw the Stephen's e-mail regarding iproute
Use the newly added TCA_HW_OFFLOAD indication from kernel
to print a consistent 'offloaded' message to user when listing qdiscs.
Signed-off-by: Yuval Mintz
---
include/uapi/linux/rtnetlink.h | 1 +
tc/tc_qdisc.c | 4
2 files changed, 5 insertions(+)
diff --git
igned-off-by: Yuval Mintz
---
Do Notice this is going to create [easy-to-solve-]conflicts with net-next,
Due to 6b3ba9146fe6 ("net: sched: allow qdiscs to handle locking").
That's also why the numbering here are apparently inconsistent [skipping
0x100].
---
include/net/sc
ty to RED qdisc")
Signed-off-by: Yuval Mintz
---
include/uapi/linux/pkt_sched.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/uapi/linux/pkt_sched.h b/include/uapi/linux/pkt_sched.h
index af3cc2f..37b5096 100644
--- a/include/uapi/linux/pkt_sched.h
+++ b/include/uapi/linux/p
Let RED utilize the new internal flag, TCQ_F_OFFLOADED,
to mark a given qdisc as offloaded instead of using a dedicated
indication.
Also, change internal logic into looking at said flag when possible.
Fixes: 602f3baf2218 ("net_sch: red: Add offload ability to RED qdisc")
Signed-off
OADED as its no longer needed.
Dave,
A bit unorthodox as it's not a fix per-se, but it's the last chance
for killing the unneeded uapi and replacing it with something better
before getting stuck with it forever.
Cheers,
Yuval
Yuval Mintz (3):
net: sched: Add TCA_HW_OFFLOAD
net: s
> Introduce NETIF_F_GRO_HW feature flag for NICs that support hardware
> GRO. With this flag, we can now independently turn on or off hardware
> GRO when GRO is on. Hardware GRO guarantees that packets can be
> re-segmented by TSO/GSO to reconstruct the original packet stream.
>
> Cc: Ariel Elio
> Advertise NETIF_F_GRO_HW and turn on or off hardware GRO based on
> NETIF_F_GRO_FW flag.
>
> Cc: Ariel Elior
> Cc: everest-linux...@cavium.com
> Signed-off-by: Michael Chan
> ---
> drivers/net/ethernet/qlogic/qede/qede_filter.c | 9 ++---
> drivers/net/ethernet/qlogic/qede/qede_main.c |
Provide a mailing list for maintenance of the module instead.
Signed-off-by: Yuval Mintz
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index beac4ee..e2dc868 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8750,7 +8750,7 @@ Q
#x27;re simply removing his corporate E-mail, replacing it with
his private one.
b. For mlxfw we're providing a mailing list as a replacement for his
contact details.
Dave,
Please consider applying this to 'net'.
Thanks,
Yuval
Yotam Gigi (1):
MAINTAINERS: Update Y
From: Yotam Gigi
For the time being I will be available in my private mail. Update both the
MAINTAINERS file and the individual modules MODULE_AUTHOR directive with
the new address.
Signed-off-by: Yotam Gigi
Signed-off-by: Yuval Mintz
---
MAINTAINERS| 4 ++--
net/ife/ife.c
> +static int bnxt_nvm_read(struct bnxt *bp, int nvm_param, int idx,
> + void *buf, int size)
> +{
> + struct hwrm_nvm_get_variable_input req = {0};
> + dma_addr_t dest_data_dma_addr;
> + void *dest_data_addr = NULL;
> + int bytesize;
> + int rc;
> +
> +
> On Tue, Oct 24, 2017 at 5:22 PM, Yuval Mintz
> wrote:
> >> Add support for permanent config parameter get/set commands. Used
> >> for persistent device configuration parameters.
> >>
> > ...
> >> + int (*perm_config_get)(struct devlink
> Adding DEVLINK_PERM_CONFIG_NUM_VF_PER_PF permanent config
> parameter. Value is permanent, so becomes the new default
> value for this device.
>
> The value sets the number of VFs per PF in SR-IOV mode.
Assuming it's meant to directly control the PCIe capability value
I think you should mentio
> Adding DEVLINK_PERM_CONFIG_SRIOV_ENABLED permanent config
> parameter. Value is permanent, so becomes the new default
> value for this device.
>
> 0 = Disable SR-IOV
> 1 = Enable SR-IOV
Does this imposes a requirement on the PCIe specifics, E.g., that the device
should no longer expose the
> Add support for permanent config parameter get/set commands. Used
> for persistent device configuration parameters.
>
...
> + int (*perm_config_get)(struct devlink *devlink,
> +enum devlink_perm_config_param param, u8
> type,
> +void *v
> >> >> On Fri, Oct 20, 2017 at 10:10 AM, Jiri Pirko wrote:
> >> >> > Fri, Oct 20, 2017 at 04:03:55PM CEST, steven.l...@broadcom.com
> wrote:
> >> >> >>On Thu, Oct 19, 2017 at 5:39 PM, Jiri Pirko wrote:
> >> >> >>> Thu, Oct 19, 2017 at 10:32:21PM CEST, yuv...@mellanox.com
> wrote:
> >> >> > A
> >> On Fri, Oct 20, 2017 at 10:10 AM, Jiri Pirko wrote:
> >> > Fri, Oct 20, 2017 at 04:03:55PM CEST, steven.l...@broadcom.com wrote:
> >> >>On Thu, Oct 19, 2017 at 5:39 PM, Jiri Pirko wrote:
> >> >>> Thu, Oct 19, 2017 at 10:32:21PM CEST, yuv...@mellanox.com wrote:
> >> > Adding DEVLINK_PERM_
> On Thu, Oct 19, 2017 at 4:21 PM, Yuval Mintz
> wrote:
> >> Subject: [PATCH net-next v2 1/6] devlink: Add permanent config
> parameter
> >> get/set operations
> >>
> >> Add support for permanent config parameter get/set commands. Used
> &g
> On Fri, Oct 20, 2017 at 10:10 AM, Jiri Pirko wrote:
> > Fri, Oct 20, 2017 at 04:03:55PM CEST, steven.l...@broadcom.com wrote:
> >>On Thu, Oct 19, 2017 at 5:39 PM, Jiri Pirko wrote:
> >>> Thu, Oct 19, 2017 at 10:32:21PM CEST, yuv...@mellanox.com wrote:
> > Adding DEVLINK_PERM_CONFIG_MSIX_VEC
> Adding DEVLINK_PERM_CONFIG_MSIX_VECTORS_PER_VF permanent
> config
> parameter. Defines number of MSI-X vectors allocated per VF.
> Value is permanent (stored in NVRAM), so becomes the new default
> value for this device.
Sounds like you're having this enforce the same configuration for all chil
> Subject: [PATCH net-next v2 1/6] devlink: Add permanent config parameter
> get/set operations
>
> Add support for permanent config parameter get/set commands. Used
> for parameters held in NVRAM, persistent device configuration.
Given some of the attributes aren't Boolean, what about an API tha
> On Thu, Oct 19, 2017 at 2:07 AM, Yuval Mintz
> wrote:
> >> +enum devlink_autoneg_protocol {
> >> + DEVLINK_AUTONEG_PROTOCOL_IEEE8023BY_BAM,
> >> + DEVLINK_AUTONEG_PROTOCOL_IEEE8023BY_CONSORTIUM,
> >> + DEVLINK_AUTONEG_PROTOCOL_IEEE8023B
> >> DEVLINK_ATTR_PERM_CFG_NPAR_BW_RESERVATION_VALID: 1 to use
> >> BW_RESERVATION setting, 0 to ignore.
> >>
> > ...
> >> DEVLINK_ATTR_PERM_CFG_NPAR_BW_LIMIT_VALID: 1 to use BW_LIMIT
> >> setting, 0 to ignore.
> >
> > While it probably ties to different fields in your NVM layout why would the
> us
> DEVLINK_ATTR_PERM_CFG_NPAR_BW_RESERVATION_VALID: 1 to use
> BW_RESERVATION setting, 0 to ignore.
>
...
> DEVLINK_ATTR_PERM_CFG_NPAR_BW_LIMIT_VALID: 1 to use BW_LIMIT
> setting, 0 to ignore.
While it probably ties to different fields in your NVM layout why would the user
require specific attribu
> DEVLINK_ATTR_PERM_CFG_MULTIFUNC_MODE: Configure multi-function
> mode; use devlink_multifunc_mode.
...
> +enum devlink_multifunc_mode {
> + DEVLINK_MULTIFUNC_MODE_ALLOWED, /* Ext switch
> activates MF */
> + DEVLINK_MULTIFUNC_MODE_FORCE_SINGFUNC,
> + DEVLINK_MULTIFUNC_MODE_NPA
> DEVLINK_ATTR_PERM_CFG_MBA_LINK_SPEED: Configured link speed
> while executing MBA host software (PXI/iSCSI); use enum
> devlink_mba_link_speed.
#4 introduces:
> DEVLINK_ATTR_PERM_CFG_PRE_OS_LINK_SPEED_D0: Configure default
> pre-OS link speed in full power (D0) state; use enum
> devlink_pre_os_
> +enum devlink_autoneg_protocol {
> + DEVLINK_AUTONEG_PROTOCOL_IEEE8023BY_BAM,
> + DEVLINK_AUTONEG_PROTOCOL_IEEE8023BY_CONSORTIUM,
> + DEVLINK_AUTONEG_PROTOCOL_IEEE8023BY,
> + DEVLINK_AUTONEG_PROTOCOL_BAM, /* Broadcom
> Autoneg Mode */
> + DEVLINK_AUTONEG_PROTOCOL_CON
> Hi, Yuval
>
> On 2017/10/15 13:14, Yuval Mintz wrote:
> >> Hi, Yuval
> >>
> >> On 2017/10/13 4:21, Yuval Mintz wrote:
> >>>> This patchset adds a new hardware offload type in mqprio before
> adding
> >>>> mqprio hardware o
> > >> This patchset adds a new hardware offload type in mqprio before
> adding
> > >> mqprio hardware offload support in hns3 driver.
Apparently Dave has already acceptedAmirtha's changes to mqprio:
https://marc.info/?l=linux-netdev&m=150803219824053&w=2
so I guess you need to revise your pa
> Hi, Yuval
>
> On 2017/10/13 4:21, Yuval Mintz wrote:
> >> This patchset adds a new hardware offload type in mqprio before adding
> >> mqprio hardware offload support in hns3 driver.
> >
> > I think one of the biggest issues in tying this to DCB conf
> This patchset adds a new hardware offload type in mqprio before adding
> mqprio hardware offload support in hns3 driver.
I think one of the biggest issues in tying this to DCB configuration is the
non-immediate [and possibly non persistent] configuration.
Scenario #1:
User is configuring mqprio
> When a driver supports both dcb and hardware offloaded mqprio, and
> user is running mqprio and dcb tool concurrently, the configuration
> set by each tool may be conflicted with each other because the dcb
(for second 'each') s/each/the
> and mqprio may be using the same hardwere offload compone
> + case VIRTCHNL_OP_REQUEST_QUEUES: {
> + struct virtchnl_vf_res_request *vfres =
> + (struct virtchnl_vf_res_request *)msg;
> + if (vfres->num_queue_pairs == adapter->num_req_queues)
> {
> + adapter->flags |=
> I40EVF_FLAG_REINIT
> hello Jiri and Yotam,
>
> On Thu, 2017-09-28 at 19:34 +0200, Jiri Pirko wrote:
> > From: Yotam Gigi
> >
> > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
> > index 19e64bf..ada8214 100644
> > --- a/include/linux/skbuff.h
> > +++ b/include/linux/skbuff.h
> > @@ -772,6 +772,7 @@ st
> Hi, Yuval
>
> On 2017/9/26 14:43, Yuval Mintz wrote:
> >> When using tc qdisc to configure DCB parameter, dcb_ops->setup_tc
> >> is used to tell hclge_dcb module to do the setup.
> >
> > While this might be a step in the right direction, this causes an
> When using tc qdisc to configure DCB parameter, dcb_ops->setup_tc
> is used to tell hclge_dcb module to do the setup.
While this might be a step in the right direction, this causes an inconsistency
in user experience - Some [well, most] vendors didn't allow the mqprio
priority mapping to affect
Looks like commit f663dd9aaf9e ("net: core: explicitly select a txq before
doing l2 forwarding")
has removed the need for this dedicated xmit function [it even explicitly
states so in its commit log message] but it hasn't removed the definition
of the ndo.
Signed-off-by: Yuval M
positive
value would be returned driver would errneously log it as an error.
Fixes: c7b7b483ccc9 ("bnx2x: Don't flush multicast MACs")
Signed-off-by: Yuval Mintz
---
Dave,
Please consider applying this to 'net'.
Thanks,
Yuval
---
drivers/net/ethernet/broadcom/bnx2x/bn
;qed*: Set rdma generic functions prefix")
Signed-off-by: Chad Dupuis
Signed-off-by: Yuval Mintz
---
include/linux/qed/qede_rdma.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/qed/qede_rdma.h b/include/linux/qed/qede_rdma.h
index 1348a16..9904617 100644
---
the SPQ into
a callback-registered mechanism, allowing registration of the relevant
event-processing logic based on the function's personality. This allows
us to tidy the code by removing protocol-specifics from a common file.
Signed-off-by: Michal Kalderon
Signed-off-by: Yuval Mintz
---
drivers
From: Michal Kalderon
Driver needs to wait for all resources to return from FW before it can send
the FUNC_CLOSE ramrod.
Signed-off-by: Michal Kalderon
Signed-off-by: Yuval Mintz
---
drivers/net/ethernet/qlogic/qed/qed_roce.c | 35 +-
1 file changed, 20 insertions
If DCBx update occurs while QPs are open, stop sending edpms until all
QPs are closed.
Signed-off-by: Yuval Mintz
---
drivers/net/ethernet/qlogic/qed/qed_dcbx.c | 8 +++
drivers/net/ethernet/qlogic/qed/qed_roce.c | 36 ++
drivers/net/ethernet/qlogic/qed
Configure device according to DCBx results so that EDPMs
made by RoCE would honor flow-control.
Signed-off-by: Yuval Mintz
---
drivers/net/ethernet/qlogic/qed/qed_dcbx.c | 16
drivers/net/ethernet/qlogic/qed/qed_reg_addr.h | 6 ++
2 files changed, 22 insertions
to make sure it contains all type
definitions it requires.
Signed-off-by: Michal Kalderon
Signed-off-by: Yuval Mintz
---
drivers/infiniband/hw/qedr/main.c | 2 +-
drivers/infiniband/hw/qedr/qedr.h | 2 +-
drivers/net/ethernet/qlog
From: Michal Kalderon
Rename the functions common to both iWARP and RoCE to have a prefix of
_rdma_ instead of _roce_.
Signed-off-by: Michal Kalderon
Signed-off-by: Yuval Mintz
---
drivers/infiniband/hw/qedr/main.c| 6 +-
drivers/net/ethernet/qlogic/qede/qede.h | 4
iWARP would require the chains to allocate/free their PBL memory
independently, so add the infrastructure to provide it externally.
Signed-off-by: Yuval Mintz
---
drivers/infiniband/hw/qedr/main.c | 2 +-
drivers/infiniband/hw/qedr/verbs.c| 6 ++---
drivers/net
unctions prefix
qed: Wait for resources before FUNC_CLOSE
qed: SPQ async callback registration
Yuval Mintz (4):
qed: Chain support for external PBL
qed: RoCE EDPM to honor PFC
qed: Disable RoCE dpm when DCBx change occurs
drivers/infiniband/hw/qedr/main.c | 10 +-
From: Michal Kalderon
Rename the functions common to both iWARP and RoCE to have a prefix of
_rdma_ instead of _roce_.
Signed-off-by: Michal Kalderon
Signed-off-by: Yuval Mintz
---
drivers/infiniband/hw/qedr/main.c| 6 +-
drivers/net/ethernet/qlogic/qede/qede.h | 4
1 - 100 of 857 matches
Mail list logo
