From: "Denis V. Lunev" <den-3ImXcnM4P+0@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: My netns patches updated to Linus' latest
Date: Thu, 19 Jul 2007 17:25:39 +0400 [thread overview]
Message-ID: <469F6653.5000004@sw.ru> (raw)
In-Reply-To: <m1myxs3mbn.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
Eric W. Biederman wrote:
> My next project is most likely going to be to dig in and make the
> loopback device a normal network device (not statically allocated)
> as a cleanup in preparation for the network namespace work.
I can do this :)
As far as I understand the code, loopback device is used in two fashions:
- as a real network device
- and as a "stable" never freed piece of memory
I presume, they should be separated.
As for device itself, there is a some sort of a template in a Pavel's
virtual ethernet device driver...
> Feel free to pick the patches apart. Especially in the core of the
> network stack.
I think that a small plan of submitting process is a good idea, at least
we will be able to coordinate the efforts and work in parallel.
> I'm hoping to start seriously submitting patches short after the merge
> window closes. So we can get a long test/review cycle.
:)
Regards,
Den
next prev parent reply other threads:[~2007-07-19 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 7:05 My netns patches updated to Linus' latest Eric W. Biederman
[not found] ` <m1myxs3mbn.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-07-19 13:25 ` Denis V. Lunev [this message]
[not found] ` <469F6653.5000004-3ImXcnM4P+0@public.gmane.org>
2007-07-19 13:53 ` Eric W. Biederman
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=469F6653.5000004@sw.ru \
--to=den-3imxcnm4p+0@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.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