From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: netdev@vger.kernel.org, h.reindl@thelounge.net,
Fedora Kernel Team <kernel-team@fedoraproject.org>
Subject: Re: order 7 allocations from xt_recent
Date: Thu, 03 Jan 2013 10:02:42 -0800 [thread overview]
Message-ID: <1357236162.21409.25394.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130103171115.GA20982@redhat.com>
On Thu, 2013-01-03 at 12:11 -0500, Dave Jones wrote:
> That 'check size and vmalloc/kmalloc accordingly' thing seems to be a pattern
> that comes up time and time again. Is it worth maybe making a more generic
> version of that instead of open-coding it each time it comes up ?
We had numerous discussions and patch submissions in the past, and this
went nowhere. I am not sure anybody wants to spend more cycles on this.
Its sad, but true.
prev parent reply other threads:[~2013-01-03 18:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 16:43 order 7 allocations from xt_recent Dave Jones
2013-01-03 16:55 ` Eric Dumazet
2013-01-03 17:11 ` Dave Jones
2013-01-03 17:26 ` Dave Jones
2013-01-03 18:00 ` Eric Dumazet
2013-01-03 19:51 ` Reindl Harald
2013-01-03 18:02 ` Eric Dumazet [this message]
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=1357236162.21409.25394.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davej@redhat.com \
--cc=h.reindl@thelounge.net \
--cc=kernel-team@fedoraproject.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