DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Simon Kågström" <simon.kagstrom@netinsight.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Unit for tx_rate in rte_eth_set_queue_rate_limit?
Date: Tue, 20 Oct 2015 14:38:54 +0200	[thread overview]
Message-ID: <2727565.cjguxIjPP1@xps13> (raw)
In-Reply-To: <56263196.9020305@netinsight.net>

2015-10-20 14:20, Simon Kågström:
> Hi!
> 
> What is the unit of the tx_rate parameter to the
> rte_eth_set_queue_rate_limit function? It's documented as
> 
> /**
>  * Set the rate limitation for a queue on an Ethernet device.
>  *
>  * @param port_id
>  *   The port identifier of the Ethernet device.
>  * @param queue_idx
>  *   The queue id.
>  * @param tx_rate
>  *   The tx rate allocated from the total link speed for this queue.
>  * @return
>  *   - (0) if successful.
>  *   - (-ENOTSUP) if hardware doesn't support this feature.
>  *   - (-ENODEV) if *port_id* invalid.
>  *   - (-EINVAL) if bad parameter.
>  */
> int rte_eth_set_queue_rate_limit(uint8_t port_id, uint16_t queue_idx,
> 			uint16_t tx_rate);
> 
> I parse this as meaning a percentage of total link speed, i.e., on a 10
> Gbps link, 50 would mean 5Gbps, 10 means 1Gbps etc. Is this correct?

It's implemented only in ixgbe:
        /* Calculate the rate factor values to set */
        rf_int = (uint32_t)link_speed / (uint32_t)tx_rate;
        rf_dec = (uint32_t)link_speed % (uint32_t)tx_rate;
        rf_dec = (rf_dec << IXGBE_RTTBCNRC_RF_INT_SHIFT) / tx_rate;

        bcnrc_val = IXGBE_RTTBCNRC_RS_ENA;
        bcnrc_val |= ((rf_int << IXGBE_RTTBCNRC_RF_INT_SHIFT) &
                IXGBE_RTTBCNRC_RF_INT_MASK_M);
        bcnrc_val |= (rf_dec & IXGBE_RTTBCNRC_RF_DEC_MASK);

So you just need to check the datasheet and send a patch to make it clear :)
Thanks

      reply	other threads:[~2015-10-20 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 12:20 Simon Kågström
2015-10-20 12:38 ` Thomas Monjalon [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=2727565.cjguxIjPP1@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=simon.kagstrom@netinsight.net \
    /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).