linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Utz Bacher" <utz.bacher@de.ibm.com>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] register_inet6addr_notifier
Date: Wed, 1 Aug 2001 20:41:29 +0200	[thread overview]
Message-ID: <OFA376540F.BE06ACC0-ONC1256A9B.0062A90E@de.ibm.com> (raw)


Hi Alexey,

> Very interesting. I am very curious, what kind of "offload" is possible
> with current stack are possible. Even if you know addresses. :-)

it's the same kind of offload we use in IPv4 -- we set the
net_device->flags to IFF_NOARP and can then talk IP to the card. That
means,
the card does ARP and the tasks of hard_header etc. itself. We register
ourselves to get informed as soon as an IP address has been added/removed
and can tell that information to the card. As soon as the card knows about
the IP addresses of the device in the stack, it can respond to ARP queries
of other nodes.

Now hardware header generation and ARP don't cost a lot of performance, but
this whole story gets in particular interesting, as an S/390 can share a
single card between partitions on the same physical box (and that's very
common; obvious by looking at the price tag of the card :-). The card
peeks into incoming packets and according to the destination address, it
passes the packets on to the right partition(s).

We have the problem, that we won't be informed about any address changes
in IPv6 other than somehow polling for them.
(un)register_inet6addr_notifier would help us here.

> What's about the patch... Do you understand that currently
> it is impossible to call notifiers for adding/deletion of each IPv6
address
> in an intelligible context? Not seeing uses of such notifiers,
> it is difficult to approve such feature because of danger of misuse
> now and even worse misuse in (near) future, when context will change.

Yes, we are fully aware, that we cannot call the notifier functions
ourselves
resp. cannot expect any useful result by doing so. We are only interested
in
being always up to date wrt. IP addresses.

Regards,
Utz

Linux for S/390 and zSeries
:wq


             reply	other threads:[~2001-08-01 18:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 18:41 Utz Bacher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-31 19:03 [PATCH] register_inet6addr_notifier Utz Bacher
2001-08-01 23:06 ` Alexey Kuznetsov
2001-08-03  9:32 ` David S. Miller

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=OFA376540F.BE06ACC0-ONC1256A9B.0062A90E@de.ibm.com \
    --to=utz.bacher@de.ibm.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@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).