netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: stephan.gatzka@gmail.com
Cc: linux1394-devel@lists.sourceforge.net,
	netdev <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>
Subject: Re: [RFC:] struct net_device_ops: Add function pointer to fill device specific ndisc information
Date: Mon, 21 Jan 2013 11:29:57 +0900	[thread overview]
Message-ID: <50FCA825.7070609@linux-ipv6.org> (raw)
In-Reply-To: <50FC6068.3020302@gmail.com>

Stephan Gatzka wrote:
> On 01/20/2013 07:47 PM, YOSHIFUJI Hideaki wrote:
> 
>> My current position is to change "mac address" to
>>
>> struct fwnet_hwaddr {
>>     u8    guid[8];
>>     u8    max_rec;
>>     u8    sspd;
>>     u8    fifo[6];
>> };
>>
> 
> That is something I'm not really convinced of. As Stefan Richter pointed out clearly, the fifo address might be different between IPv4 and IPv6 communication.

We could have multiple "net_device"s per single physical
interface at the same time, then.

Multicast is a big issue.  Because IPv6 is fan of
multicast, and it uses link-local multicast as its
core infrastructure.  Without infrastructure to
support it, I'm not going to agree.

And, firewire driver does not seem to support zerocopy
(fragmented skb) support.  It help performance.

--yoshfuji

  reply	other threads:[~2013-01-21  2:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-20 17:52 [RFC:] struct net_device_ops: Add function pointer to fill device specific ndisc information Stephan Gatzka
2013-01-20 18:47 ` YOSHIFUJI Hideaki
2013-01-20 21:23   ` Stephan Gatzka
2013-01-21  2:29     ` YOSHIFUJI Hideaki [this message]
2013-01-21  6:25       ` Stephan Gatzka
2013-01-21  7:39         ` Stefan Richter
2013-01-21 11:50           ` YOSHIFUJI Hideaki
2013-01-21 19:25           ` Stephan Gatzka
2013-01-21 19:57             ` YOSHIFUJI Hideaki
2013-01-21 21:16               ` Stephan Gatzka
2013-01-27 14:43                 ` Stefan Richter
2013-01-27 17:21                   ` Stephan Gatzka
2013-01-27 18:20                     ` Stephan Gatzka
2013-01-27 18:25                       ` YOSHIFUJI Hideaki
2013-01-27 19:28                     ` YOSHIFUJI Hideaki
2013-01-27 23:26                       ` Stefan Richter
2013-01-21 11:50         ` YOSHIFUJI Hideaki
2013-01-21  8:09     ` Stefan Richter
2013-01-21 12:04       ` YOSHIFUJI Hideaki
2013-01-21 13:15         ` Stefan Richter
2013-01-21  6:37   ` Stephan Gatzka
2013-01-21 12:16     ` YOSHIFUJI Hideaki
2013-01-20 21:22 ` Waskiewicz Jr, Peter P
2013-01-21  6:17   ` Stephan Gatzka
2013-01-21  8:28     ` Stefan Richter
2013-01-21 12:32       ` YOSHIFUJI Hideaki
2013-01-21 14:15         ` YOSHIFUJI Hideaki

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=50FCA825.7070609@linux-ipv6.org \
    --to=yoshfuji@linux-ipv6.org \
    --cc=davem@davemloft.net \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=stephan.gatzka@gmail.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).