From: Stephen Hemminger <stephen@networkplumber.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: linville@tuxdriver.com, Paul Greenwalt <paul.greenwalt@intel.com>,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [ethtool 1/1] ethtool: Add DMA Coalescing support
Date: Fri, 25 Aug 2017 15:57:16 -0700 [thread overview]
Message-ID: <20170825155716.630e6f72@xeon-e3> (raw)
In-Reply-To: <20170825223910.54989-1-jeffrey.t.kirsher@intel.com>
On Fri, 25 Aug 2017 15:39:10 -0700
Jeff Kirsher <jeffrey.t.kirsher@intel.com> wrote:
> diff --git a/ethtool-copy.h b/ethtool-copy.h
> index 06fc04c..4bb91eb 100644
> --- a/ethtool-copy.h
> +++ b/ethtool-copy.h
> @@ -400,6 +400,7 @@ struct ethtool_modinfo {
> * a TX interrupt, when the packet rate is above @pkt_rate_high.
> * @rate_sample_interval: How often to do adaptive coalescing packet rate
> * sampling, measured in seconds. Must not be zero.
> + * @dmac: How many usecs to store packets before moving to host memory.
> *
> * Each pair of (usecs, max_frames) fields specifies that interrupts
> * should be coalesced until
> @@ -450,6 +451,7 @@ struct ethtool_coalesce {
> __u32 tx_coalesce_usecs_high;
> __u32 tx_max_coalesced_frames_high;
> __u32 rate_sample_interval;
> + __u32 dmac;
> };
>
Because of backwards ABI compatibility, it is not safe to extend
an existing structure.
prev parent reply other threads:[~2017-08-25 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 22:39 [ethtool 1/1] ethtool: Add DMA Coalescing support Jeff Kirsher
2017-08-25 22:57 ` Stephen Hemminger [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=20170825155716.630e6f72@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=paul.greenwalt@intel.com \
--cc=sassmann@redhat.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 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.