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:29:12 +0000 [thread overview]
Message-ID: <20090227092912.GC4156@ff.dom.local> (raw)
In-Reply-To: <20090227.011615.104197338.davem@davemloft.net>
On Fri, Feb 27, 2009 at 01:16:15AM -0800, David Miller wrote:
> From: Jarek Poplawski <jarkao2@gmail.com>
> Date: Fri, 27 Feb 2009 09:12:16 +0000
...
> > 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:
>
> Note there is already a function that could do this and which needs to
> hit all the same RX entrypoints just like this check would.
>
> And that is skb_bond_should_drop().
>
> We could rename that to skb_rx_should_drop() and put the netpoll
> checks there.
>
> There is some weird conditinalization of skb_bond_should_drop()'s call
> in netif_receive_skb() but that should be easy to change to suit our
> needs. Perhaps by putting the calculation of the netdevice bonding
> pointers into that function.
Yes, it would be nice to have it in this one place, but I guess
currently for vlans we depend on vlan_hwaccel_do_receive(), and there
are probably some reasons it's so far from the bond check.
Jarek P.
next prev parent reply other threads:[~2009-02-27 9:29 UTC|newest]
Thread overview: 44+ 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
2009-02-27 9:16 ` David Miller
2009-02-27 9:29 ` Jarek Poplawski [this message]
2009-03-01 7:38 ` Herbert Xu
2009-03-01 8:12 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2017-05-11 15:17 Frank Vosberg
2017-05-11 16:57 ` Randy Dunlap
2017-05-12 5:56 ` Michal Hocko
2009-12-09 7:01 kernel problem werner
2009-12-09 7:01 werner
2009-12-04 19:48 werner
2009-12-04 19:47 werner
2009-12-03 7:40 werner
2009-12-04 15:41 ` Steven Rostedt
2009-12-07 14:50 ` Mel Gorman
2009-12-07 20:48 ` Andrew Morton
2009-12-07 21:09 ` Jens Axboe
2007-01-13 10:56 Suresh Chandra Mannava
2004-06-22 16:54 Kernel problem Juhani Pirttilahti
2004-06-22 17:18 ` William Lee Irwin III
2004-06-22 19:47 ` Juhani Pirttilahti
2004-06-22 22:43 ` Juhani Pirttilahti
2004-06-23 8:33 ` Geert Uytterhoeven
2002-05-20 6:04 Kernel Problem Brinley Craig
1998-05-18 18:07 Kernel problem Stephan van Hienen
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=20090227092912.GC4156@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 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.