From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: gregkh@linuxfoundation.org, haiyangz@microsoft.com,
netdev@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] net/hyperv: Add flow control based on hi/low watermark
Date: Wed, 28 Mar 2012 16:54:17 -0400 (EDT) [thread overview]
Message-ID: <20120328.165417.1083579824641543055.davem@davemloft.net> (raw)
In-Reply-To: <1332957900.2624.38.camel@bwh-desktop.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Wed, 28 Mar 2012 19:05:00 +0100
> On Mon, 2012-03-26 at 19:12 -0400, David Miller wrote:
>> From: Greg KH <gregkh@linuxfoundation.org>
>> Date: Mon, 26 Mar 2012 16:10:17 -0700
>>
>> > David, please do NOT apply this as-is.
>>
>> BTW, ethtool had controls exactly for stuff like this.
>
> Not sure what you're thinking of...? We have pause frame control but I
> don't think that's applicable.
As I understand this, this situation is really about interrupt flow
control, and for that we have the interrupt moderation ethtool
settings.
next prev parent reply other threads:[~2012-03-28 20:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 22:18 [PATCH 0/1] net/hyperv: Add flow control based on hi/low watermark Haiyang Zhang
2012-03-26 22:12 ` David Miller
2012-03-26 22:18 ` [PATCH 1/1] " Haiyang Zhang
2012-03-26 23:10 ` Greg KH
2012-03-26 23:12 ` David Miller
2012-03-28 18:05 ` Ben Hutchings
2012-03-28 20:54 ` David Miller [this message]
2012-03-27 1:17 ` Haiyang Zhang
-- strict thread matches above, loose matches on Subject: below --
2012-03-27 22:23 [PATCH 0/1] " Haiyang Zhang
2012-03-27 22:23 ` [PATCH 1/1] " Haiyang Zhang
2012-03-27 22:20 ` Greg KH
2012-03-27 22:25 ` Haiyang Zhang
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=20120328.165417.1083579824641543055.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiyangz@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
/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).