All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Alex Layton <alex@layton.in>, linux-can <linux-can@vger.kernel.org>
Subject: Re: can-j1939: semantics question
Date: Thu, 12 Nov 2015 09:39:45 +0100	[thread overview]
Message-ID: <20151112083945.GA30235@airbook.vandijck-laurijssen.be> (raw)
In-Reply-To: <5643A9CA.8060509@hartkopp.net>


> On 11.11.2015 20:52, Kurt Van Dijck wrote:
> 
> >I eventually got into investigating the necessary changes to drop
> >iproute2 from can-j1939.
> >We somewhat agreed that opening a can-j1939 socket and binding
> >to a CAN interface should activate can-j1939 processing for that
> >interface.
> >But how about deactivation?
> >Should the last can-j1939 socket on a CAN iface deactivate can-j1939 for
> >that iface when that socket closes?
> 
> At least this sounds like some kind of natural behaviour.
> 
> What would be the other option?

A special tool, intentionally not called 'ip' :-), that turns off
j1939 processing. Looks bad.

I'll stick to the 'natural behaviour'.

> 
> Would you still monitor address claiming inside the kernel without doing
> anything else?

no. And noone needs it anyway.

> 
> Or is the address claiming in user space the last application that closes
> the last socket anyway??

indeed, address claiming requires an open socket.

Thanks,
Kurt

      reply	other threads:[~2015-11-12  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 19:52 can-j1939: semantics question Kurt Van Dijck
2015-11-11 20:49 ` Oliver Hartkopp
2015-11-12  8:39   ` Kurt Van Dijck [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=20151112083945.GA30235@airbook.vandijck-laurijssen.be \
    --to=dev.kurt@vandijck-laurijssen.be \
    --cc=alex@layton.in \
    --cc=linux-can@vger.kernel.org \
    --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.