From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: yevgenyp@mellanox.co.il, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/3] mlx4_en: moderate frequency of TX completions
Date: Thu, 23 Feb 2012 16:47:56 -0500 (EST) [thread overview]
Message-ID: <20120223.164756.887751433359593643.davem@davemloft.net> (raw)
In-Reply-To: <1330032380.2511.17.camel@bwh-desktop>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Thu, 23 Feb 2012 21:26:20 +0000
> And it's pretty obvious the hardware has to also send a completion when
> the queue is empty. I hope.
Right and we know of several chips that don't.
next prev parent reply other threads:[~2012-02-23 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:34 [PATCH net-next 2/3] mlx4_en: moderate frequency of TX completions Yevgeny Petrilin
2012-02-23 19:44 ` David Miller
2012-02-23 21:13 ` Ben Hutchings
2012-02-23 21:26 ` Ben Hutchings
2012-02-23 21:47 ` David Miller [this message]
2012-02-23 21:46 ` 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=20120223.164756.887751433359593643.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.co.il \
/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).