netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Pierre Tosoni" <jp.tosoni-eYuUwLwYA0BQFI55V6+gNQ@public.gmane.org>
To: "'Stephen Hemminger'"
	<stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>,
	"'Linus Lüssing'"
	<linus.luessing-djzkFPsfvsizQB+pC5nmwQ@public.gmane.org>
Cc: <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"'David S . Miller'"
	<davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
	<bridge-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>,
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"'Felix Fietkau'" <nbd-Vt+b4OUoWG0@public.gmane.org>
Subject: RE: [PATCH net-next] bridge: multicast to unicast
Date: Mon, 9 Jan 2017 09:36:55 +0100	[thread overview]
Message-ID: <002f01d26a53$88c8da60$9a5a8f20$@acksys.fr> (raw)
In-Reply-To: <20170106191356.43740a26@xeon-e3>

> -----Message d'origine-----
> De : linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org [mailto:linux-wireless-
> owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org] De la part de Stephen Hemminger
> Envoyé : samedi 7 janvier 2017 04:14
> À : Linus Lüssing
> Cc : netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; David S . Miller; bridge-cunTk1MwBs/ROKNJybVBZg@public.gmane.org
> foundation.org; linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; linux-
> wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org; Felix Fietkau
> Objet : Re: [PATCH net-next] bridge: multicast to unicast
> 
> On Mon,  2 Jan 2017 20:32:14 +0100
> Linus Lüssing <linus.luessing-djzkFPsfvsizQB+pC5nmwQ@public.gmane.org> wrote:
> 
> > This feature is intended for interface types which have a more
> > reliable and/or efficient way to deliver unicast packets than
> > broadcast ones (e.g. wifi).
> 
> 
> Why is this not done in MAC80211 rather than  bridge?

OTOH mac80211 has more information to decide whether it is more economic to send one multicast or several unicast.
It depends on the bitrate of each station, number of stations and the (not necessarily slower) bitrate of multicasts.

      parent reply	other threads:[~2017-01-09  8:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 19:32 [PATCH net-next] bridge: multicast to unicast Linus Lüssing
2017-01-03 11:58 ` Nikolay Aleksandrov via Bridge
2017-01-03 13:15 ` Felix Fietkau
2017-01-06 12:47 ` Johannes Berg
2017-01-06 13:52   ` Felix Fietkau
2017-01-06 13:54     ` Johannes Berg
2017-01-06 13:54       ` Felix Fietkau
2017-01-07 10:32       ` M. Braun
2017-01-07 14:55         ` Linus Lüssing
2017-01-09  8:08           ` Johannes Berg
2017-01-09 11:44             ` M. Braun
2017-01-09 12:15               ` Johannes Berg
2017-01-09 15:25                 ` michael-dev
2017-01-09 15:47                   ` Johannes Berg
2017-01-09 21:23               ` Linus Lüssing
2017-01-09 21:30                 ` Stephen Hemminger
2017-01-10  4:18                   ` Linus Lüssing
2017-01-10 10:56                     ` Johannes Berg
2017-01-10 17:17                       ` Dave Taht
2017-01-10 17:23                         ` Felix Fietkau
2017-01-10 18:24                           ` Dave Taht
2017-01-10 21:27                       ` Felix Fietkau
2017-01-11 11:26                         ` IgorMitsyanko
2017-01-11 11:30                           ` Felix Fietkau
2017-01-11 12:15                             ` IgorMitsyanko
2017-01-11 12:21                               ` Felix Fietkau
2017-01-07 15:15   ` Linus Lüssing
2017-01-09  8:05     ` Johannes Berg
2017-01-09 12:42       ` Linus Lüssing
2017-01-09 12:44         ` Johannes Berg
2017-01-09 23:12           ` Linus Lüssing
2017-01-11  9:17             ` Johannes Berg
2017-01-07  3:13 ` Stephen Hemminger
2017-01-07 15:06   ` Linus Lüssing
2017-01-09  8:36   ` Jean-Pierre Tosoni [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='002f01d26a53$88c8da60$9a5a8f20$@acksys.fr' \
    --to=jp.tosoni-eyuuwlwya0bqfi55v6+gnq@public.gmane.org \
    --cc=bridge-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
    --cc=linus.luessing-djzkFPsfvsizQB+pC5nmwQ@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nbd-Vt+b4OUoWG0@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org \
    /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).