From: ebiederm@xmission.com (Eric W. Biederman)
To: Lucian Adrian Grijincu <lucian.grijincu@gmail.com>
Cc: Anca Emanuel <anca.emanuel@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Octavian Purdila <tavi@cs.pub.ro>,
"David S . Miller" <davem@davemloft.net>,
Alexey Dobriyan <adobriyan@gmail.com>,
Damien Millescamps <damien.millescamps@6wind.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: v6: faster tree-based sysctl implementation
Date: Wed, 07 Dec 2011 16:19:53 -0800 [thread overview]
Message-ID: <m162hrgbiu.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <CAPLs8y-sc7CZw2Yb11A-jTEMmTYva==XHgCqK1UmWN6_HX0rfA@mail.gmail.com> (Lucian Adrian Grijincu's message of "Wed, 7 Dec 2011 03:44:29 +0200")
Lucian Adrian Grijincu <lucian.grijincu@gmail.com> writes:
> On Wed, Dec 7, 2011 at 2:08 AM, Anca Emanuel <anca.emanuel@gmail.com> wrote:
>> You can ask Stephen Rothwell to include your tree in next.
>> git://github.com/luciang/linux-2.6-new-sysctl.git v6-new-sysctl-alg
>
>
> Thank you Anca, but I don't want to pollute Stephen's linux-next tree ATM.
> I'd wait until a maintainer chimes in and agrees that this approach is
> sound.
Which is my cue to say that I am behind the power curve in reviewing
this. I will see if I can get to this before the end of the week.
Doing this and getting it right is definitely something we need to do.
We do need to be careful so that the code we wind up with is not just
faster but more maintainable than what we have today.
Thanks for still pushing this,
Eric
next prev parent reply other threads:[~2011-12-08 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 7:55 v6: faster tree-based sysctl implementation Lucian Adrian Grijincu
2011-12-06 14:11 ` Anca Emanuel
2011-12-06 14:33 ` Lucian Adrian Grijincu
2011-12-06 16:47 ` Damien Millescamps
2011-12-06 18:42 ` Benjamin LaHaise
2011-12-06 23:42 ` Anca Emanuel
2011-12-07 0:08 ` Anca Emanuel
2011-12-07 1:44 ` Lucian Adrian Grijincu
2011-12-08 0:19 ` Eric W. Biederman [this message]
2011-12-16 8:15 ` Eric W. Biederman
2011-12-18 8:05 ` 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=m162hrgbiu.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=adobriyan@gmail.com \
--cc=anca.emanuel@gmail.com \
--cc=damien.millescamps@6wind.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lucian.grijincu@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tavi@cs.pub.ro \
/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