From: Erwan Velu <erwanaliasr1@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, jesse.brandeburg@intel.com,
bruce.w.allan@intel.com, alexander.h.duyck@intel.com,
peter.p.waskiewicz.jr@intel.com, john.ronciak@intel.com
Subject: Re: [PATCH] e100: expose broadcast_disabled as a module option
Date: Mon, 26 Apr 2010 16:45:54 +0200 [thread overview]
Message-ID: <p2nb43bf5491004260745m58ed54b4ue50c2bd3431c9941@mail.gmail.com> (raw)
In-Reply-To: <y2lb43bf5491004260149x23beb95dqc9e177d9a6ecc679@mail.gmail.com>
2010/4/26 Erwan Velu <erwanaliasr1@gmail.com>:
After some research, here come my status :
> Does any one you could help me understanding what should be the good way to
> 1- enabled/disabled IFF_BROADCAST for a given interface
Looks like the current code isn't taking care of a possible changing
of IFF_BROADCAST. I can find some code in net/core/dev.c to handle
MULTICAST or PROMISC but nothing for BROADCAST.
do I have to implement one ?
> 2- populate this changes to the driver
Looks like I need then to add a .ndo_change_rx_flags function to
manage this changes.
Does someone confirm this is the way to go ?
prev parent reply other threads:[~2010-04-26 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <l2nb43bf5491004231314i13503c67yeccfc54bc1cae850@mail.gmail.com>
2010-04-23 20:22 ` [PATCH] e100: expose broadcast_disabled as a module option Jeff Kirsher
2010-04-23 20:58 ` Stephen Hemminger
2010-04-23 21:03 ` Erwan Velu
2010-04-23 22:02 ` Stephen Hemminger
2010-04-26 8:49 ` Erwan Velu
2010-04-26 14:45 ` Erwan Velu [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=p2nb43bf5491004260745m58ed54b4ue50c2bd3431c9941@mail.gmail.com \
--to=erwanaliasr1@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@vyatta.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).