public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@linuxpower.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: gigabit ethernet small-packet performance
Date: Sun, 5 Nov 2000 16:17:52 -0500	[thread overview]
Message-ID: <20001105161752.A13140@xi.linuxpower.cx> (raw)
In-Reply-To: <200011051507.eA5F7KX30823@amsterdam.lcs.mit.edu> <20001105134518.E12776@xi.linuxpower.cx> <20001105224047.A18024@home.ds9a.nl>
In-Reply-To: <20001105224047.A18024@home.ds9a.nl>; from ahu@ds9a.nl on Sun, Nov 05, 2000 at 10:40:48PM +0100

On Sun, Nov 05, 2000 at 10:40:48PM +0100, bert hubert wrote:
> On Sun, Nov 05, 2000 at 01:45:18PM -0500, Gregory Maxwell wrote:
> 
> > Hmm.. Kernel code written in C++..
> > You people are nuts. :)
> 
> Nobody benefits from having such a closed mind. While I don't wish to imply
> that C++ is 'ready' for general use in the kernel, there is a useful subset
> of C++ that might one day be.

I didn't mean it that way. I though it was interesting in light of the
earlier flame war. Esp considering they appear to be using virtual
functions.

The 'you people are nuts. :)' was meant as a positive statement. 
Don't you know? All breakthroughs come from crazy people. :)

> Oh, and please let us not launch another huge discussion about this subject.
> I just want to state that having a closed mind is not going to help us.

Their code speaks for itself. It outperforms the Linux code and is more
flexible. 

Although, I tend to see that as a case for additional optimization of the
current Linux code... C++ can be a very useful development tool with the
potential to increase modularity and simplify development. However,
run-time abstraction will always be a performance loss.

I was happy to see the prior flame war end with 'Let the code speak', I only
brought this up here to draw some attention to Click from a C++ in the kernel
prospective, i.e. They are using C++ in the kernel (without extensive kernel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-05 21:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05 15:07 gigabit ethernet small-packet performance Robert Morris
2000-11-05 18:32 ` Mr. James W. Laferriere
2000-11-05 18:45 ` Gregory Maxwell
2000-11-05 21:40   ` bert hubert
2000-11-05 21:17     ` Gregory Maxwell [this message]
2000-11-07 19:44 ` Jes Sorensen
2000-11-08 15:23 ` Jamie Lokier

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=20001105161752.A13140@xi.linuxpower.cx \
    --to=greg@linuxpower.cx \
    --cc=linux-kernel@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