[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140516153902.GG8346@casper.infradead.org>
Date: Fri, 16 May 2014 16:39:02 +0100
From: Thomas Graf <tgraf@...g.ch>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Ben Greear <greearb@...delatech.com>, davem@...emloft.net,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next] pktgen: Add NOINIT option to leave packet data
uninitialized
On 05/16/14 at 08:26am, Eric Dumazet wrote:
> On Fri, 2014-05-16 at 16:20 +0100, Thomas Graf wrote:
>
> > I'm aware of the work and I agree. That is perfectly fine if the
> > produced skbs do not get enqueued and modified. Otherwise the clone
> > and COW will undo the gain again. I need pktgen to produce large,
> > linear skbs with a unique flow for each individual packet. Hence this
> > optimization ;-)
>
> pktgen is a tool for us kernel net developers.
>
> I doubt more than 20 people on this planet used it in the last 12
> months, expecting crazy numbers out of one core, while a simple user
> space program can outperform pktgen these days.
>
> So if you need a very specific hack, you can do it on your local tree ;)
Which I already stated I'd be fine with ;)
But for the sake of the argument... Since you mention that pktgen is
clearly a tool for us kernel net developers. That would (hopefully)
imply that everybody using it knows what they are doing. Just like
somebody running kgdb, dumping kernel memory with kdump, or running
perf. I don't see why the choice of deliberately exposing kernel memory
in either of these cases is an issue.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists