From: Ben Hutchings <bhutchings@solarflare.com>
To: Tom Herbert <therbert@google.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v3 02/10] net: Add queue state xoff flag for stack
Date: Mon, 28 Nov 2011 17:46:09 +0000 [thread overview]
Message-ID: <1322502369.26733.5.camel@bwh-desktop> (raw)
In-Reply-To: <alpine.DEB.2.00.1111222139180.14467@pokey.mtv.corp.google.com>
On Tue, 2011-11-22 at 21:52 -0800, Tom Herbert wrote:
> Create separate queue state flags so that either the stack or drivers
> can turn on XOFF. Added a set of functions used in the stack to determine
> if a queue is really stopped (either by stack or driver)
[...]
> static inline int netif_tx_queue_stopped(const struct netdev_queue *dev_queue)
> {
> - return test_bit(__QUEUE_STATE_XOFF, &dev_queue->state);
> + return test_bit(__QUEUE_STATE_DRV_XOFF, &dev_queue->state);
> }
[...]
> +static inline int netif_xmit_stopped(const struct netdev_queue *dev_queue)
> {
> - return dev_queue->state & QUEUE_STATE_XOFF_OR_FROZEN;
> + return dev_queue->state & QUEUE_STATE_ANY_XOFF;
> +}
[...]
The difference in names here doesn't really suggest the difference in
semantics. I think they will be easy to confuse.
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.
prev parent reply other threads:[~2011-11-28 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 5:52 [PATCH v3 02/10] net: Add queue state xoff flag for stack Tom Herbert
2011-11-28 17:46 ` Ben Hutchings [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=1322502369.26733.5.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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 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).