All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Vadai <amirv@mellanox.com>
To: "David S. Miller" <davem@davemloft.net>,
	John Fastabend <john.r.fastabend@intel.com>
Cc: <netdev@vger.kernel.org>, Roland Dreier <roland@purestorage.com>,
	Oren Duer <oren@mellanox.com>,
	Yevgeny Petrilin <yevgenyp@mellanox.com>
Subject: Re: [PATCH 0/8] net/mlx4_en: DCB QoS support
Date: Tue, 20 Mar 2012 13:29:11 +0200	[thread overview]
Message-ID: <4F686A07.4070401@mellanox.com> (raw)
In-Reply-To: <1331659323-12904-1-git-send-email-amirv@mellanox.com>

On 03/13/2012 07:21 PM, Amir Vadai wrote:
> DCBX version 802.1qaz is supported.
> User Priority (UP) is set in QP context instead of in WQE (QP Work Queue
> Element), which means that all traffic from a queue will have the same UP.
> UP is also set for untagged traffic to be able to classify such traffic too.
>
> Mapping from sk_prio to User Priority is done by sch_mqprio mapping. Although
> confusingly sch_mqprio maps sk_prio to something called TC, it is not related
> to DCBX's TC, and is interpreted by mlx4_en driver as UP.
>
> The Current HW based QoS mechanism which was introduced in commit 4f57c087de9
> "net: implement mechanism for HW based QOS" is in orientation to ETS traffic
> class. Patch 7/8 introduces an approach which allow to use this mechanism also
> with hardware who has queues per user priority (UP). After the change,
> __skb_tx_hash() will direct a flow to a tx ring from a range of tx rings. This
> range is defined by the caller function by the specific HW. If TC based queues,
> the range is by TC number and for UP based queues, the range is by UP.
>
> Amir Vadai (8):
>    net/mlx4_en: Force user priority by QP attribute
>    net/mlx4_core: set port QoS attributes
>    net/mlx4_en: DCB QoS support
>    net/mlx4_en: Set max rate-limit for a TC
>    net/mlx4_en: sk_prio<=>  UP for untagged traffic
>    IB/rdma_cm: TOS<=>  UP mapping for IBoE
>    net: support tx_ring per UP in HW based QoS mechanism
>    net/mlx4_en: num cores tx rings for every UP
>
>   drivers/infiniband/core/cma.c                     |   35 ++++-
>   drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c   |   11 +-
>   drivers/net/ethernet/mellanox/mlx4/Kconfig        |   12 ++
>   drivers/net/ethernet/mellanox/mlx4/Makefile       |    1 +
>   drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c    |  215 +++++++++++++++++++++
>   drivers/net/ethernet/mellanox/mlx4/en_main.c      |    6 +-
>   drivers/net/ethernet/mellanox/mlx4/en_netdev.c    |   64 ++++++-
>   drivers/net/ethernet/mellanox/mlx4/en_port.h      |    2 +
>   drivers/net/ethernet/mellanox/mlx4/en_resources.c |    6 +-
>   drivers/net/ethernet/mellanox/mlx4/en_rx.c        |    4 +-
>   drivers/net/ethernet/mellanox/mlx4/en_sysfs.c     |  120 ++++++++++++
>   drivers/net/ethernet/mellanox/mlx4/en_tx.c        |   20 +-
>   drivers/net/ethernet/mellanox/mlx4/mlx4.h         |   20 ++
>   drivers/net/ethernet/mellanox/mlx4/mlx4_en.h      |   38 +++-
>   drivers/net/ethernet/mellanox/mlx4/port.c         |   62 ++++++
>   include/linux/mlx4/cmd.h                          |    4 +
>   include/linux/mlx4/device.h                       |    3 +
>   include/linux/mlx4/qp.h                           |    3 +-
>   include/linux/netdevice.h                         |   12 +-
>   include/linux/skbuff.h                            |    3 +-
>   net/core/dev.c                                    |   10 +-
>   21 files changed, 615 insertions(+), 36 deletions(-)
>   create mode 100644 drivers/net/ethernet/mellanox/mlx4/en_dcb_nl.c
>   create mode 100644 drivers/net/ethernet/mellanox/mlx4/en_sysfs.c
>


Hi Dave,

Patches 7-8 who deal with the interaction between the kernel HW QoS 
constructs to the queue selection logic are still under discussion with 
John and some changes might be needed there.
At this point, we ask for patches 1-6 to be pulled in, and continue the 
discussion from there.

Thanks,
Amir

  parent reply	other threads:[~2012-03-20 11:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 17:21 [PATCH 0/8] net/mlx4_en: DCB QoS support Amir Vadai
2012-03-13 17:21 ` [PATCH 1/8] net/mlx4_en: Force user priority by QP attribute Amir Vadai
2012-03-13 17:21 ` [PATCH 2/8] net/mlx4_core: set port QoS attributes Amir Vadai
2012-03-13 17:21 ` [PATCH 3/8] net/mlx4_en: DCB QoS support Amir Vadai
2012-03-13 17:21 ` [PATCH 4/8] net/mlx4_en: Set max rate-limit for a TC Amir Vadai
2012-03-13 18:26   ` John Fastabend
2012-03-14 10:31     ` Amir Vadai
2012-03-13 19:16   ` Dave Taht
2012-03-14 10:42     ` Amir Vadai
2012-03-13 17:22 ` [PATCH 5/8] net/mlx4_en: sk_prio <=> UP for untagged traffic Amir Vadai
2012-03-13 17:22 ` [PATCH 6/8] IB/rdma_cm: TOS <=> UP mapping for IBoE Amir Vadai
2012-03-13 17:22 ` [PATCH 7/8] net: support tx_ring per UP in HW based QoS mechanism Amir Vadai
2012-03-13 18:23   ` John Fastabend
2012-03-14 10:09     ` Amir Vadai
2012-03-14 21:36       ` John Fastabend
2012-03-15 10:05         ` Amir Vadai
2012-03-16  7:16           ` John Fastabend
2012-03-13 17:22 ` [PATCH 8/8] net/mlx4_en: num cores tx rings for every UP Amir Vadai
2012-03-20 11:29 ` Amir Vadai [this message]
2012-03-20 19:58   ` [PATCH 0/8] net/mlx4_en: DCB QoS support David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F686A07.4070401@mellanox.com \
    --to=amirv@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=john.r.fastabend@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=oren@mellanox.com \
    --cc=roland@purestorage.com \
    --cc=yevgenyp@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.