From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Xie He <xie.he.0141@gmail.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Network Development <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: [PATCH net-next v2 4/4] net: hdlc_fr: Add support for any Ethertype
Date: Thu, 29 Oct 2020 20:53:17 -0400 [thread overview]
Message-ID: <CA+FuTSdy38GOTKRr9Ze3jvfTQqxR7s_c67J0z75AFZ-yihAVuw@mail.gmail.com> (raw)
In-Reply-To: <CAJht_EPggyhiaROvReNJ4hCwQ6+Z0wf4zHADrSAaT8jBE0J+1w@mail.gmail.com>
On Thu, Oct 29, 2020 at 8:49 PM Xie He <xie.he.0141@gmail.com> wrote:
>
> On Thu, Oct 29, 2020 at 4:53 PM Xie He <xie.he.0141@gmail.com> wrote:
> >
> > > Does it make sense to define a struct snap_hdr instead of manually
> > > casting all these bytes?
> >
> > > And macros or constant integers to self document these kinds of fields.
> >
> > Yes, we can define a struct snap_hdr, like this:
> >
> > struct snap_hdr {
> > u8 oui[3];
> > __be16 pid;
> > } __packed;
> >
> > And then the fr_snap_parse function could be like this:
> >
> > static int fr_snap_parse(struct sk_buff *skb, struct pvc_device *pvc)
> > {
> > struct snap_hdr *hdr = (struct snap_hdr *)skb->data;
> >
> > if (hdr->oui[0] == OUI_ETHERTYPE_1 &&
> > hdr->oui[1] == OUI_ETHERTYPE_2 &&
> > hdr->oui[2] == OUI_ETHERTYPE_3) {
> > if (!pvc->main)
> > return -1;
> > skb->dev = pvc->main;
> > skb->protocol = hdr->pid; /* Ethertype */
> > skb_pull(skb, 5);
> > skb_reset_mac_header(skb);
> > return 0;
> >
> > } else if (hdr->oui[0] == OUI_802_1_1 &&
> > hdr->oui[1] == OUI_802_1_2 &&
> > hdr->oui[2] == OUI_802_1_3) {
> > if (hdr->pid == htons(PID_ETHER_WO_FCS)) {
> >
> > Would this look cleaner?
>
> Actually I don't think this is significantly cleaner than the previous
> version of code. A reader of this code may still wonder what are the
> values of all these macros, and he/she may still want to look up the
> values of them. The comment in the previous version of code has made
> the meaning of these values very clear, and the reader of the code
> would not need to go to another place of this file to find the values.
>
> The struct snap_hdr eliminates a cast, but only one cast. So it might
> not be very necessary, either. Introducing this struct also makes the
> reader need to go to another place of this file to look up the
> definition of this struct. So it does not significantly improve the
> readability (IMHO).
Thanks for coding up an example. Yes, seeing the alternative, I agree.
next prev parent reply other threads:[~2020-10-30 0:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 13:18 [PATCH net-next v2 0/4] net: hdlc_fr: Add support for any Ethertype Xie He
2020-10-28 13:18 ` [PATCH net-next v2 1/4] net: hdlc_fr: Simpify fr_rx by using "goto rx_drop" to drop frames Xie He
2020-10-28 13:18 ` [PATCH net-next v2 2/4] net: hdlc_fr: Change the use of "dev" in fr_rx to make the code cleaner Xie He
2020-10-28 13:18 ` [PATCH net-next v2 3/4] net: hdlc_fr: Improve the initial check when we receive an skb Xie He
2020-10-28 13:18 ` [PATCH net-next v2 4/4] net: hdlc_fr: Add support for any Ethertype Xie He
2020-10-29 17:23 ` Willem de Bruijn
2020-10-29 23:53 ` Xie He
2020-10-30 0:49 ` Xie He
2020-10-30 0:53 ` Willem de Bruijn [this message]
2020-10-30 0:50 ` Willem de Bruijn
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=CA+FuTSdy38GOTKRr9Ze3jvfTQqxR7s_c67J0z75AFZ-yihAVuw@mail.gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xie.he.0141@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).