From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Xu, Rosen" <rosen.xu@intel.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"nithin.dabilpuram@cavium.com" <nithin.dabilpuram@cavium.com>
Subject: Re: [dpdk-dev] [RFC] ethdev: add tail drop API for traffic management
Date: Thu, 16 Aug 2018 08:54:55 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891268E79E2D9@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <0E78D399C70DA940A335608C6ED296D73A1CB17C@SHSMSX104.ccr.corp.intel.com>
> -----Original Message-----
> From: Xu, Rosen
> Sent: Tuesday, August 14, 2018 7:45 AM
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>;
> Lu, Wenzhuo <wenzhuo.lu@intel.com>; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> nithin.dabilpuram@cavium.com
> Subject: RE: [dpdk-dev] [RFC] ethdev: add tail drop API for traffic
> management
>
>
>
> > -----Original Message-----
> > From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com]
> > Sent: Tuesday, August 14, 2018 14:06
> > To: Xu, Rosen <rosen.xu@intel.com>
> > Cc: dev@dpdk.org; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>;
> Lu,
> > Wenzhuo <wenzhuo.lu@intel.com>; Singh, Jasvinder
> > <jasvinder.singh@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>;
> > nithin.dabilpuram@cavium.com
> > Subject: Re: [dpdk-dev] [RFC] ethdev: add tail drop API for traffic
> > management
> >
> > -----Original Message-----
> > > Date: Mon, 13 Aug 2018 15:53:32 +0800
> > > From: Rosen Xu <rosen.xu@intel.com>
> > > To: dev@dpdk.org
> > > CC: cristian.dumitrescu@intel.com, wenzhuo.lu@intel.com,
> > > jasvinder.singh@intel.com, rosen.xu@intel.com, ferruh.yigit@intel.com
> > > Subject: [dpdk-dev] [RFC] ethdev: add tail drop API for traffic
> > > management
> > > X-Mailer: git-send-email 1.8.3.1
> > >
> > >
> > > This patch introduces new ethdev generic Tail Drop API for Traffic
> > > Management, which is yet another standard congestion management
> > > offload for Ethernet devices.
> > >
> > > Tail Drop is about packets dropping when they arrive on a congested
> > > interface buffer. It's one mode of congestion management for hierarchy
> > > leaf nodes.
> > >
> > > There are two configuration parameters for Tail Drop:
> > > 1. Buffer Depth: determine the depth of receive fifo for packet RX.
> >
This scheme is a sort of WRED-lite, so Rosen and I decided to look at fitting the driver he's currently working on under the WRED scheme; we can take another look at this if any significant issues are to be found (unlikely).
Regards,
Cristian
prev parent reply other threads:[~2018-08-16 8:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 7:53 Rosen Xu
2018-08-13 19:23 ` Stephen Hemminger
2018-08-14 6:05 ` Jerin Jacob
2018-08-14 6:45 ` Xu, Rosen
2018-08-16 0:56 ` Xu, Rosen
2018-08-16 8:54 ` Dumitrescu, Cristian [this message]
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=3EB4FA525960D640B5BDFFD6A3D891268E79E2D9@IRSMSX107.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nithin.dabilpuram@cavium.com \
--cc=rosen.xu@intel.com \
--cc=wenzhuo.lu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).