From: "Roland Dreier" <rdreier@cisco.com>
To: "David Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, ggrundstrom@NetEffect.com,
openib-general@openib.org
Subject: Re: [PATCH 4 of 9] NetEffect 10Gb RNIC Driver: kernel driver header files
Date: Thu, 26 Oct 2006 17:33:44 -0700 [thread overview]
Message-ID: <adafyda61hz.fsf@cisco.com> (raw)
In-Reply-To: <20061026.171657.43852974.davem@davemloft.net> (David Miller's message of "Thu, 26 Oct 2006 17:16:57 -0700 (PDT)")
> I fear this is exactly the kind of stuff that we didn't want
> to see start going into the kernel, and we've resisted the
> TCP/IP stack offload stuff in the infiniband layer exactly
> for this reason.
We're definitely not going to merge a second TCP stack in any form.
- R.
next prev parent reply other threads:[~2006-10-27 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 0:14 [PATCH 4 of 9] NetEffect 10Gb RNIC Driver: kernel driver header files Glenn Grundstrom
2006-10-27 0:16 ` David Miller
2006-10-27 0:33 ` Roland Dreier [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-27 0:06 Glenn Grundstrom
2006-10-27 0:09 ` David Miller
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=adafyda61hz.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=davem@davemloft.net \
--cc=ggrundstrom@NetEffect.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.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;
as well as URLs for NNTP newsgroup(s).