All of lore.kernel.org
 help / color / mirror / Atom feed
From: ayuj <ayuj.verma@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: Configure traffic class to bringup DCB in back-to-back setup
Date: Thu, 14 Jul 2016 09:35:33 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160714T112300-449@post.gmane.org> (raw)
In-Reply-To: 57867E13.3040708@gmail.com

John Fastabend <john.fastabend <at> gmail.com> writes:

> So at the moment it appears to be configured to use 802.1QAZ spec which
> superseded the older spec even though lldpad supports both. Note the
> tool itself really requires some spec knowledge to use correctly. The
> spec to read is 802.1Q.
> 
> To configure it back-to-back (typical scenario is connected to a DCB
> enabled switch where your administrator would setup the switch and this
> would autoneg just fine) the servers need to be setup manually.
> 
> Perhaps reading if you haven't already the man page for lldptool and
> lldptool-ets, lldptool-pfc would help. From the ets man page this
> should kick things off,
> 
> #lldptool -T -i eth2 -V ETS-CFG \
>           tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets \
>           up2tc=0:0,1:1,2:2,3:3,4:4,5:5,6:6,7:7 \
>           tcbw=12,12,12,12,13,13,13,13
> 
> #lldptool -T -i eth2 -V ETS-REC \
>            tsa=0:ets,1:ets,2:ets,3:ets,4:ets,5:ets,6:ets,7:ets \
>            up2tc=0:0,1:1,2:2,3:3,4:4,5:5,6:6,7:7 \
>            tcbw=12,12,12,12,13,13,13,13
> 
> Thanks,
> John
> 
> 
Hi John,
 
I have gone through  lldptool and lldptool-ets man pages. My query is how to
categorize traffic. 

My aim is to allocate bandwidth to different type of traffic(may be based on
port or protocol) using DCB( ETS/PFC) functionality.

Thanks
-Ayuj

      reply	other threads:[~2016-07-14  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13  9:09 Configure traffic class to bringup DCB in back-to-back setup ayuj
2016-07-13 17:44 ` [Intel-wired-lan] " John Fastabend
2016-07-13 17:44   ` John Fastabend
2016-07-14  9:35   ` ayuj [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=loom.20160714T112300-449@post.gmane.org \
    --to=ayuj.verma@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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.