All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: dev@sebastianhaas.info, linux-can@vger.kernel.org
Subject: Re: [RFC] can: Introducing CANFD for af_can & can-raw
Date: Wed, 21 Mar 2012 14:19:40 +0100	[thread overview]
Message-ID: <4F69D56C.9050607@pengutronix.de> (raw)
In-Reply-To: <20120321125130.GC3372@vandijck-laurijssen.be>

[-- Attachment #1: Type: text/plain, Size: 2289 bytes --]

On 03/21/2012 01:51 PM, Kurt Van Dijck wrote:
>>>> What about
>>>> the RX path? We can just use the new 64 byte CAN frames and have to
>>>> tweak the CAN_RAW if the read from the userspace is too small.
>>> You may have noticed that I did not need to do anything
>>> in the receive path in order to receive longer frames.
>>>
>>> look at this block in raw_recvmsg:
>>>
>>> 	if (size < skb->len)
>>> 		msg->msg_flags |= MSG_TRUNC;
>>> 	else
>>> 		size = skb->len;
>>>
>>> Even today already, you can recv. with smaller or bigger buffers than
>>> the actual CAN frame.
>>
>> ...using an unmodified mainline kernel?
> 
> Must be. yes!
> I think that's good.

Indeed. I wasn't aware of this.

>>> I did try to let the kernel work with 64bytes, and still use
>>> 8byte frames in userspace. that all works, especially since noone
>>> seems to test for MSG_TRUNC.
>>
>> Have you checked _all_ CAN userspace applications? :P
>> We cannot break the ABI.
> I mentioned cansend & candump.
> I realize there's a lot of work ahead. I just started, and tried
> not to touch too much, and yet prove it can work.
> 
> I agree that we cannot break the current ABI.
> 
>>
>>> An improvement that just crosses my mind is something like:
>>>
>>> 	int real_len;
>>>
>>> 	real_len = offsetof(struct can_frame, data) +
>>> 		((struct can_frame)skb->data)->dlc;
>>> 	if (size < real_len)
>>> 		msg->msg_flags |= MSG_TRUNC;
>>> 	else
>>> 		size = real_len;
>>>
>>> Such would modify the ABI a bit more, but prevents copying unused bytes
>>> and avoids unnecessary MSG_TRUNC flags.
>>
>> I suggest to copy the full 8 bytes of data if dlc <= 8, for full ABI
>> compatibility.
> 
> Do we then agree that it is desired not to do this beyond the first 8 bytes?
> Moreover, we could depend this on the function parameter 'size'. If it
> is 16bytes, do as before, else do the new trick. Did I miss something then?

Yes, if 16 bytes is the length of the current struct can_frame.

Marc
-- 
Pengutronix e.K.                  | Marc Kleine-Budde           |
Industrial Linux Solutions        | Phone: +49-231-2826-924     |
Vertretung West/Dortmund          | Fax:   +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686  | http://www.pengutronix.de   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-03-21 13:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21  9:10 [RFC] can: Introducing CANFD for af_can & can-raw Kurt Van Dijck
     [not found] ` <E1SAIM4-0007a6-Sf@smtprelay03.ispgateway.de>
2012-03-21 11:05   ` Kurt Van Dijck
2012-03-21 11:43     ` Marc Kleine-Budde
2012-03-21 12:08       ` Kurt Van Dijck
2012-03-21 12:32         ` Marc Kleine-Budde
2012-03-21 12:51           ` Kurt Van Dijck
2012-03-21 13:19             ` Marc Kleine-Budde [this message]
2012-03-21 13:21           ` Oliver Hartkopp
2012-03-21 13:53             ` Kurt Van Dijck
2012-03-21 14:49               ` Oliver Hartkopp
2012-03-21 15:26                 ` Oliver Hartkopp
2012-03-22  9:03                 ` Kurt Van Dijck
2012-03-21 14:56               ` Wolfgang Grandegger
2012-03-21 15:05                 ` Oliver Hartkopp
2012-03-22  9:24                   ` Kurt Van Dijck
2012-03-22  9:32                     ` Marc Kleine-Budde
2012-03-22  9:38                     ` Wolfgang Grandegger
2012-03-22 10:13                       ` Kurt Van Dijck
2012-03-23 11:01                         ` Wolfgang Grandegger
2012-03-22  9:57                   ` Kurt Van Dijck
2012-03-22 10:06                     ` Wolfgang Grandegger
2012-03-22 10:35                       ` Kurt Van Dijck
2012-03-22 11:00                         ` Wolfgang Grandegger
2012-03-22 12:25                           ` Oliver Hartkopp
2012-03-22 12:47                             ` Kurt Van Dijck
2012-03-21 13:29           ` Alexander Stein
2012-03-21 13:34             ` Kurt Van Dijck
2012-03-21 13:51             ` Marc Kleine-Budde
2012-03-21 15:47               ` Alexander Stein

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=4F69D56C.9050607@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=dev@sebastianhaas.info \
    --cc=linux-can@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 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.