netdev - Re: [RFC 2/2] ethtool: Add support for DMA Coalescing feature config to ethtool.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110617.145420.866989290749857501.davem@davemloft.net>
Date:	Fri, 17 Jun 2011 14:54:20 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	carolyn.wyborny@...el.com
Cc:	netdev@...r.kernel.org, bhutchings@...arflare.com
Subject: Re: [RFC 2/2] ethtool: Add support for DMA Coalescing feature
 config to ethtool.

From: "Wyborny, Carolyn" <carolyn.wyborny@...el.com>
Date: Fri, 17 Jun 2011 08:50:11 -0700

> I will add a fuller description of the feature in my updated patch.
> I thought the feature was more well known. Quick description is that
> it's a power saving feature that causes the adapter to coalesce its
> DMA writes at low traffic times to save power on the platform by
> reducing wakeups.  The parameter is intended as a simple u32 value,
> not just an on or off, but also to allow a variety of configuration
> by adapter vendors, with validation of the input on the driver side.
> Since I left out the implementation in my patch, this wasn't clear.
> I will also fix this in my next submission.

The value cannot have adapter specific meaning, you must define it
precisely and in a generic manner, such that the user can specify the
same setting across different card types.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html