public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: netdev@vger.kernel.org, containers@lists.osdl.org
Cc: benjamin.thery@bull.net, dlezcano@fr.ibm.com
Subject: dynamically allocated dst_ops
Date: Thu, 30 Oct 2008 07:26:22 +0300	[thread overview]
Message-ID: <20081030042622.GA21196@x200.localdomain> (raw)

They are bogus and should be implanted into struct net directly.
In garbage collector hook, just use container_of() (once) to get struct net.
->dst_net is useless after that.

I'm going to use this trick for xfrm.

And if someone has ideas on how to overcome header difficulties, please,
submit a patch.

             reply	other threads:[~2008-10-30  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  4:26 Alexey Dobriyan [this message]
2008-10-31 13:34 ` dynamically allocated dst_ops Daniel Lezcano
  -- strict thread matches above, loose matches on Subject: below --
2008-10-30  4:22 Alexey Dobriyan
2008-10-30  5:36 ` 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=20081030042622.GA21196@x200.localdomain \
    --to=adobriyan@gmail.com \
    --cc=benjamin.thery@bull.net \
    --cc=containers@lists.osdl.org \
    --cc=dlezcano@fr.ibm.com \
    --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