From: Julius Niedworok <julius.n@gmx.net>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: linux-wireless@vger.kernel.org, ga58taw@mytum.de,
David Hildenbrand <david@redhat.com>,
nc@net.in.tum.de, "David S. Miller" <davem@davemloft.net>,
Johannes Berg <johannes@sipsolutions.net>,
Edward Cree <ecree@solarflare.com>,
Jiri Pirko <jiri@mellanox.com>,
Ido Schimmel <idosch@mellanox.com>,
Petr Machata <petrm@mellanox.com>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Alexander Duyck <alexander.h.duyck@intel.com>,
Amritha Nambiar <amritha.nambiar@intel.com>,
Li RongQing <lirongqing@baidu.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] mac80211: Use IFF_ECHO to force delivery of tx_status frames
Date: Tue, 26 Feb 2019 14:13:51 +0100 [thread overview]
Message-ID: <6A213CBE-0B6A-466A-B721-E6A728D4888D@gmx.net> (raw)
In-Reply-To: <c522f2e0-1bef-8679-45f7-707854918820@hartkopp.net>
Hi Oliver,
> On 26.02.2019 12:04, Oliver Hartkopp wrote:
>
> Hi Julius,
>
(..)
>
> The reason for IFF_ECHO was, that the data frame which is sent onto the wire (by one application) is not visible to all the other applications on the same (local) host. Therefore a successful transmission on the wire triggers the 'echo' of the sent content into the local host.
>
Thank you for the explanation - I can adjust the comment, if you like to.
> So what are you getting back after you enabled IFF_ECHO on your mac80211 device?
>
> Is it just a 'status' about a sent packet, or is it the packet ('full content') itself?
We are actually getting back the full content of the packet. So it matches the behaviour of the 'echo' in CAN.
>
> Regards,
> Oliver
>
Many thanks,
Julius
next prev parent reply other threads:[~2019-02-26 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 9:40 [PATCH RFC] mac80211: Use IFF_ECHO to force delivery of tx_status frames Julius Niedworok
2019-02-26 11:04 ` Oliver Hartkopp
2019-02-26 13:13 ` Julius Niedworok [this message]
2019-02-26 13:33 ` Johannes Berg
2019-02-28 9:05 ` Julius Niedworok
2019-03-01 8:32 ` Johannes Berg
2019-03-02 15:16 ` Julius Niedworok
2019-03-06 20:02 ` [PATCH RFC v2] mac80211: debugfs option to force TX status frames Julius Niedworok
2019-03-07 15:42 ` Kalle Valo
2019-03-07 19:30 ` ga58taw
2019-03-11 14:03 ` Kalle Valo
2019-03-11 14:52 ` Jeremy Sowden
2019-03-19 15:07 ` Julius Niedworok
2019-03-20 12:13 ` Jeremy Sowden
2019-03-28 20:01 ` [PATCH v3] " Julius Niedworok
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=6A213CBE-0B6A-466A-B721-E6A728D4888D@gmx.net \
--to=julius.n@gmx.net \
--cc=alexander.h.duyck@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=david@redhat.com \
--cc=ecree@solarflare.com \
--cc=ga58taw@mytum.de \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=johannes@sipsolutions.net \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=nc@net.in.tum.de \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.com \
--cc=socketcan@hartkopp.net \
/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.