From: Ben Hutchings <bhutchings@solarflare.com>
To: Eli Cohen <eli@dev.mellanox.co.il>, David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: invalid requirement from ethtool?
Date: Mon, 15 Aug 2011 18:24:00 +0100 [thread overview]
Message-ID: <1313429040.2731.17.camel@bwh-desktop> (raw)
In-Reply-To: <20110726124222.GA4842@mtldesk30>
On Tue, 2011-07-26 at 15:42 +0300, Eli Cohen wrote:
> Hi,
> I see the following text in include/linux/ethtool.h and wonder what is
> the reasoning for requiring that both params cannot be zero. I could
> not track when and who inserted this text as it dates before git was
> used to track kernel code, but my feeling is that is related to a
> specific hardware limitation.
>
> /* How many packets to delay an RX interrupt after
> * a packet arrives. If 0, only rx_coalesce_usecs is
> * used. It is illegal to set both usecs and max frames
> * to zero as this would cause RX interrupts to never be
> * generated.
> */
> __u32 rx_max_coalesced_frames;
>
> /* How many packets to delay a TX interrupt after
> * a packet is sent. If 0, only tx_coalesce_usecs is
> * used. It is illegal to set both usecs and max frames
> * to zero as this would cause TX interrupts to never be
> * generated.
> */
> __u32 tx_max_coalesced_frames;
>
> I found this in tg3 driver:
> /* No rx interrupts will be generated if both are zero */
> if ((ec->rx_coalesce_usecs == 0) &&
> (ec->rx_max_coalesced_frames == 0))
> return -EINVAL;
>
> However, bnx2 for example allows setting both to zero.
>
> I think both params zero should be allowed and mean coalescing is not
> operational, thus we can remove these comments from ethtool.h
If coalescing is not operational, the maximum number of completions
before an interrupt is 1. So logically {rx,tx}_max_coalesced_frames
should be 1, right? Although the comment does say 'How many packets ...
after ...' which implies that the value of the field must be 1 less than
the wanted maximum, i.e. 0, which is supposedly invalid.
The first implementation of ethtool coalescing control was in tg3, so it
should be a useful reference.
David, I know you maintained tg3 for some time so I assume you have a
hardware reference. Can you confirm whether a value of 1 in
HOSTCC_{RX,TX}MAX_FRAMES results in an interrupt after 1 completion or
after 2 completions?
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-08-15 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 12:42 invalid requirement from ethtool? Eli Cohen
2011-07-28 5:43 ` David Miller
2011-07-28 7:23 ` Eli Cohen
2011-07-28 7:37 ` David Miller
2011-07-28 10:22 ` Ben Hutchings
2011-07-28 14:55 ` Eli Cohen
2011-08-15 17:24 ` Ben Hutchings [this message]
2011-08-15 20:49 ` 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=1313429040.2731.17.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=eli@dev.mellanox.co.il \
--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 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).