From: David Miller <davem@davemloft.net>
To: eldad@fogrefinery.com
Cc: kaber@trash.net, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8021q/vlan: process NETDEV_GOING_DOWN
Date: Tue, 29 May 2012 20:40:40 -0400 (EDT) [thread overview]
Message-ID: <20120529.204040.644013889059321702.davem@davemloft.net> (raw)
In-Reply-To: <1338330635-27259-1-git-send-email-eldad@fogrefinery.com>
From: Eldad Zack <eldad@fogrefinery.com>
Date: Wed, 30 May 2012 00:30:35 +0200
> In the current flow, when you take down a physical device that has
> VLANs configured on it, the NETDEV_GOING_DOWN notification will be
> sent too late, i.e., no data can be sent to the wire anymore.
Why do you need to send data? Any queued up data should be purged not
sent.
next prev parent reply other threads:[~2012-05-30 0:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 22:30 [PATCH] 8021q/vlan: process NETDEV_GOING_DOWN Eldad Zack
2012-05-30 0:40 ` David Miller [this message]
2012-05-30 19:11 ` Eldad Zack
2012-05-30 20:27 ` David Miller
2012-05-30 21:47 ` Eldad Zack
2012-05-30 21:50 ` David Miller
2012-05-30 22:02 ` Eldad Zack
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=20120529.204040.644013889059321702.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eldad@fogrefinery.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).