From: David Miller <davem@davemloft.net>
To: adobriyan@gmail.com
Cc: netdev@vger.kernel.org, containers@vger.kernel.org
Subject: Re: dynamically allocated dst_ops
Date: Wed, 29 Oct 2008 22:36:17 -0700 (PDT) [thread overview]
Message-ID: <20081029.223617.130281870.davem@davemloft.net> (raw)
In-Reply-To: <20081030042241.GA15999@x200.localdomain>
From: Alexey Dobriyan <adobriyan@gmail.com>
Date: Thu, 30 Oct 2008 07:22:41 +0300
> 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.
This sounds good to me :)
next prev parent reply other threads:[~2008-10-30 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 4:22 dynamically allocated dst_ops Alexey Dobriyan
2008-10-30 5:36 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-30 4:26 Alexey Dobriyan
2008-10-31 13:34 ` Daniel Lezcano
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=20081029.223617.130281870.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adobriyan@gmail.com \
--cc=containers@vger.kernel.org \
--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).