From: Prashant Sreedharan <prashant@broadcom.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Michael Chan <mchan@broadcom.com>,
Ben Hutchings <ben@decadent.org.uk>, <siva.kallam@broadcom.com>
Subject: Re: Question regarding {G,S}CHANNELS API
Date: Fri, 8 Jan 2016 10:17:13 -0800 [thread overview]
Message-ID: <1452277033.13470.43.camel@prashant> (raw)
In-Reply-To: <20160108114139.74a35521@jkicinski-Precision-T1700>
On Fri, 2016-01-08 at 11:41 +0000, Jakub Kicinski wrote:
> The point of my email was that it's a bit cumbersome to express such
> configuration with the current ethtool API. Therefore I'm asking if
> it's preferred to use:
> ethtool ethX -L rx N tx M
For tg3 driver this is the preferred way
> in this case, or:
> ethtool ethX -L combined N tx/rx abs(M-N)
tg3 will ignore the combined option and only consider separate tx / rx
values here. Combined will always be displayed as 0 to the user.
We understand your concern, and agree that the internal implementation
does not assign separate irq's to each tx, rx rings when tx/rx option is
used by user. With limited number of status blocks (max 4) and a HW bug
due to which not more than 1 TX ring is recommended to be enabled, it
was implemented in this manner.
prev parent reply other threads:[~2016-01-08 18:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 15:43 Question regarding {G,S}CHANNELS API Jakub Kicinski
2016-01-07 21:24 ` Prashant Sreedharan
2016-01-08 11:41 ` Jakub Kicinski
2016-01-08 18:17 ` Prashant Sreedharan [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=1452277033.13470.43.camel@prashant \
--to=prashant@broadcom.com \
--cc=ben@decadent.org.uk \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=siva.kallam@broadcom.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).