netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: herbert@gondor.apana.org.au, ash@sevsky.net, netdev@vger.kernel.org
Subject: Re: Kernel problem
Date: Fri, 27 Feb 2009 09:12:16 +0000	[thread overview]
Message-ID: <20090227091216.GB4156@ff.dom.local> (raw)
In-Reply-To: <20090227.005907.94994126.davem@davemloft.net>

On Fri, Feb 27, 2009 at 12:59:07AM -0800, David Miller wrote:
> From: Jarek Poplawski <jarkao2@gmail.com>
> Date: Fri, 27 Feb 2009 08:41:10 +0000
> 
> > Probably I miss something, but I'm not sure it's really necessary in
> > all (non-VLAN) entry points. Of course it's an optimization to drop
> > these things early, but there is a lot off mess with replicating
> > various parts of netif_receive_skb() in so many places.
> > 
> > As a matter of fact, I wonder why it can't be done in one place, e.g.
> > netif_nit_deliver(), which was created partly for similar problems.
> 
> I think we do need to hit all possible entry points.
> 
> How would you be able to handle it in netif_nit_deliver()?
> Functions like netif_receive_skb() open-code the delivery to
> network taps, they don't actually call netif_receive_skb().

netif_nit_deliver() is a place called by vlan with orig skb->dev, so
it could be reused to check for netpoll btw. Of course, return value
should be added etc. and maybe name changed too. It could be
something like this:

netif_receive_skb()

	if (skb->vlan_tci) {
		ret = vlan_hwaccel_do_receive(skb);
		if (ret)
			return ret;
	}
...

Jarek P.

  reply	other threads:[~2009-02-27  9:12 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 11:43 Kernel problem Denis Romanenko
2009-02-26  9:39 ` Herbert Xu
2009-02-26  9:38   ` Denys Fedoryschenko
2009-02-26 10:56   ` Jarek Poplawski
2009-02-26 11:24     ` Denis Romanenko
2009-02-26 12:00       ` Jarek Poplawski
2009-02-26 12:47         ` Jarek Poplawski
2009-02-26 12:51           ` Denis Romanenko
2009-02-26 13:17             ` Jarek Poplawski
2009-02-26 11:56     ` Herbert Xu
2009-02-26 12:10       ` David Miller
2009-02-26 13:06         ` Herbert Xu
2009-02-26 13:19           ` Jarek Poplawski
2009-02-27  4:11           ` Herbert Xu
2009-02-27  8:03             ` David Miller
2009-02-27 11:45               ` Herbert Xu
2009-02-27 13:24                 ` David Miller
2009-02-27  8:41             ` Jarek Poplawski
2009-02-27  8:59               ` David Miller
2009-02-27  9:12                 ` Jarek Poplawski [this message]
2009-02-27  9:16                   ` David Miller
2009-02-27  9:29                     ` Jarek Poplawski
2009-03-01  7:38                     ` Herbert Xu
2009-03-01  8:12                       ` 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=20090227091216.GB4156@ff.dom.local \
    --to=jarkao2@gmail.com \
    --cc=ash@sevsky.net \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@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).