netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: David Miller <davem@davemloft.net>,
	kaber@trash.net, netdev@vger.kernel.org
Subject: Re: [PATCH take 2] net_sched: Add qdisc __NET_XMIT_BYPASS flag
Date: Tue, 5 Aug 2008 17:50:01 +0200	[thread overview]
Message-ID: <20080805155001.GA2526@ami.dom.local> (raw)
In-Reply-To: <20080805154350.27523juch31xgjcw@hayate.ip6>

On Tue, Aug 05, 2008 at 03:43:50PM +0300, Jussi Kivilinna wrote:
> Quoting "Jarek Poplawski" <jarkao2@gmail.com>:
>
>> On Mon, Aug 04, 2008 at 09:35:35PM +0300, Jussi Kivilinna wrote:
>>> Quoting "Jarek Poplawski" <jarkao2@gmail.com>:
>>>
>>> This seems to also make sure that when returning 'full'
>>> NET_XMIT_SUCCESS, skb pointer is safe(r?) to use now.
>>
>> I guess so... At least theoretically - I was mainly afraid of
>> redirecting, which isn't fully implemented yet. On the other hand,
>> outwards of qdiscs there is still no difference.
>>
>
> How about making skb shared before passing into qdisc tree?
> That would make skb usage safe after qdisc enqueues.

It's a bit costly (atomics), so there should be a good reason for this.
It should be first checked if there is real danger. And if it's only
for more exact stats, I'm not sure it's worth of it.

Jarek P.

>
> ---
>
> diff --git a/include/net/sch_generic.h b/include/net/sch_generic.h
> index c5bb130..9cf06fc 100644
> --- a/include/net/sch_generic.h
> +++ b/include/net/sch_generic.h
> @@ -352,10 +352,16 @@ static inline int qdisc_enqueue(struct sk_buff  
> *skb, struct Qdisc *sch)
>         return sch->enqueue(skb, sch);
>  }
>
> -static inline int qdisc_enqueue_root(struct sk_buff *skb, struct Qdisc *sch)
> +static inline int qdisc_enqueue_root(struct sk_buff *__skb, struct  
> Qdisc *sch)
>  {
> +       struct sk_buff *skb = skb_get(__skb);
> +       int ret;
> +
>         qdisc_skb_cb(skb)->pkt_len = skb->len;
> -       return qdisc_enqueue(skb, sch);
> +       ret = qdisc_enqueue(skb, sch);
> +       kfree_skb(skb);
> +
> +       return ret;
>  }
>
>  static inline int __qdisc_enqueue_tail(struct sk_buff *skb, struct  
> Qdisc *sch,
>

  reply	other threads:[~2008-08-05 15:50 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31 17:14 [PATCH] net_sched: Add qdisc __NET_XMIT_STOLEN flag Jarek Poplawski
2008-08-01  6:15 ` Patrick McHardy
2008-08-01  7:58   ` Jarek Poplawski
2008-08-01 10:19   ` [PATCH] net_sched: Add qdisc __NET_XMIT_BYPASS flag Jarek Poplawski
2008-08-04  1:25     ` David Miller
2008-08-04  6:28       ` [PATCH take 2] " Jarek Poplawski
2008-08-04  6:42         ` David Miller
2008-08-04  6:51           ` Jarek Poplawski
2008-08-04  8:55           ` [PATCH 1/2 respin] net_sched: Add qdisc __NET_XMIT_STOLEN flag Jarek Poplawski
2008-08-05  5:38             ` David Miller
2008-08-04  8:57           ` [PATCH 2/2 respin] net_sched: Add qdisc __NET_XMIT_BYPASS flag Jarek Poplawski
2008-08-05  6:14             ` David Miller
2008-08-05  6:34               ` Jarek Poplawski
2008-08-05  6:31                 ` David Miller
2008-08-05  6:47                   ` Jarek Poplawski
2008-08-04 18:35         ` [PATCH take 2] " Jussi Kivilinna
2008-08-04 21:03           ` Jarek Poplawski
2008-08-05 12:43             ` Jussi Kivilinna
2008-08-05 15:50               ` Jarek Poplawski [this message]
2008-08-06 19:42                 ` qdisc_enqueue, NET_XMIT_SUCCESS and kfree_skb (Was: Re: [PATCH take 2] net_sched: Add qdisc __NET_XMIT_BYPASS flag) Jussi Kivilinna
2008-08-06 21:52                   ` Jarek Poplawski
2008-08-07  3:26                     ` qdisc_enqueue, NET_XMIT_SUCCESS and kfree_skb David Miller
2008-08-07  5:09                       ` David Miller
2008-08-07  6:24                         ` Jarek Poplawski
2008-08-07 10:09                         ` Jarek Poplawski
2008-08-07 10:10                           ` David Miller
2008-08-07 10:31                             ` Jarek Poplawski
2008-08-07 10:45                               ` David Miller
2008-08-07 11:39                                 ` Jarek Poplawski
2008-08-07 11:36                           ` Jussi Kivilinna
2008-08-07 12:05                             ` Jarek Poplawski
2008-08-18  6:52                             ` David Miller
2008-08-19 12:50                               ` Herbert Xu
2008-08-19 13:08                                 ` Patrick McHardy
2008-08-19 13:11                                   ` Herbert Xu
2008-08-19 13:20                                     ` Patrick McHardy
2008-08-19 13:42                                       ` Herbert Xu
2008-08-19 20:10                                         ` Denys Fedoryshchenko
2008-08-19 20:21                                           ` Jarek Poplawski
2008-08-19 20:26                                           ` David Miller
2008-08-07 11:40                     ` qdisc_enqueue, NET_XMIT_SUCCESS and kfree_skb (Was: Re: [PATCH take 2] net_sched: Add qdisc __NET_XMIT_BYPASS flag) Jussi Kivilinna
2008-08-07 12:23                       ` Jarek Poplawski
2008-08-05 21:22               ` [PATCH take 2] net_sched: Add qdisc __NET_XMIT_BYPASS flag David Miller
2008-08-04  6:48       ` [PATCH take 3] " Jarek Poplawski

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=20080805155001.GA2526@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jussi.kivilinna@mbnet.fi \
    --cc=kaber@trash.net \
    --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).