From: Johannes Berg <johannes@sipsolutions.net>
To: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
backports@vger.kernel.org
Subject: Re: [PATCH] backports: backport IFF_NO_QUEUE net_device flag
Date: Wed, 26 Aug 2015 00:05:11 +0200 [thread overview]
Message-ID: <1440540311.2376.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1440531399-29379-1-git-send-email-emmanuel.grumbach@intel.com> (sfid-20150825_213646_779513_F10D303E)
On Tue, 2015-08-25 at 22:36 +0300, Emmanuel Grumbach wrote:
> commit fa8187c96471c49419c25d4ec3299d17d3f274b2
> Author: Phil Sutter <phil@nwl.cc>
> Date: Thu Aug 13 19:01:06 2015 +0200
>
> net: declare new net_device priv_flag IFF_NO_QUEUE
>
> This private net_device flag can be set by drivers to inform that a
> device runs fine without a qdisc attached. This was formerly done by
> setting tx_queue_len to zero.
>
> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> ---
> backport/backport-include/linux/netdevice.h | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/backport/backport-include/linux/netdevice.h
> b/backport/backport-include/linux/netdevice.h
> index 95189be..94d8613 100644
> --- a/backport/backport-include/linux/netdevice.h
> +++ b/backport/backport-include/linux/netdevice.h
> @@ -292,4 +292,9 @@ netdev_features_t passthru_features_check(struct
> sk_buff *skb,
> })
> #endif /* netdev_alloc_pcpu_stats */
>
> +#if LINUX_VERSION_CODE < KERNEL_VERSION(4,2,0)
> +#ifndef IFF_NO_QUEUE
> +#define IFF_NO_QUEUE 1<<26
> +#endif
>
That doesn't really help, does it? Need to add a semantic patch to
backport this with an ifdef to set the tx_queue_len to 0 in the older
kernel case?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2015-08-25 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 19:36 [PATCH] backports: backport IFF_NO_QUEUE net_device flag Emmanuel Grumbach
2015-08-25 22:05 ` Johannes Berg [this message]
2015-08-26 2:42 ` Grumbach, Emmanuel
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=1440540311.2376.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=emmanuel.grumbach@intel.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.