linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Egil Hjelmeland <privat@egil-hjelmeland.no>
To: Andrew Lunn <andrew@lunn.ch>
Cc: vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: dsa: lan9303: IGMP handling
Date: Fri, 10 Nov 2017 19:22:11 +0100	[thread overview]
Message-ID: <49a8be62-683e-aac6-b3f3-eef7295a49ca@egil-hjelmeland.no> (raw)
In-Reply-To: <20171110140719.GC11872@lunn.ch>



Den 10. nov. 2017 15:07, skrev Andrew Lunn:
>> skb->offload_fwd_mark calculation is a candidate for consolidation into the
>> DSA core. The calculation can probably be more polished when done at a point
>> where DSA has updated skb.
> 
> Hi Egil
> 
> Yes, at some point we should do this. But at the moment it is too
> early. We don't have enough experience with what the different
> switches need. I would like to see 4 or more devices doing it before
> we consolidate the code into the core.
> 

Absolutely. My point was rather I prefer not spend time polishing this 
snippet right now, because it will probably be refactored later anyway.

One steppingstone could be to make reusable helper-functions in 
net/dsa/dsa_priv.h. But I leave that to device #2 that implement this ;-)

> 	    Andrew
> 

Egil

  reply	other threads:[~2017-11-10 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 11:54 [PATCH net-next 0/2] net: dsa: lan9303: IGMP handling Egil Hjelmeland
2017-11-10 11:54 ` [PATCH net-next 1/2] net: dsa: lan9303: Set up trapping of IGMP to CPU port Egil Hjelmeland
2017-11-10 14:10   ` Andrew Lunn
2017-11-10 11:54 ` [PATCH net-next 2/2] net: dsa: lan9303: Clear offload_fwd_mark for IGMP Egil Hjelmeland
2017-11-13 11:00   ` Egil Hjelmeland
2017-11-13 13:02     ` Andrew Lunn
2017-11-13 13:04       ` Egil Hjelmeland
2017-11-10 14:07 ` [PATCH net-next 0/2] net: dsa: lan9303: IGMP handling Andrew Lunn
2017-11-10 18:22   ` Egil Hjelmeland [this message]
2017-11-11 12:50 ` David 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=49a8be62-683e-aac6-b3f3-eef7295a49ca@egil-hjelmeland.no \
    --to=privat@egil-hjelmeland.no \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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).