From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: "Pedro M. Rodrigues" <pmanuel@myrealbox.com>,
chen_xiangping@emc.com, "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Tcp/ip offload card driver
Date: 10 May 2002 12:36:06 -0600 [thread overview]
Message-ID: <m1n0v7zw89.fsf@frodo.biederman.org> (raw)
In-Reply-To: <FA2F59D0E55B4B4892EA076FF8704F553D1A42@srgraham.eng.emc.com> <3CDBFF5B.32550.1364FB2@localhost> <3CDBE7EB.9060605@mandrakesoft.com>
Jeff Garzik <jgarzik@mandrakesoft.com> writes:
> Pedro M. Rodrigues wrote:
>
> > Actually there is. Think iSCSI. Have a look at this article at LinuxJournal
> > - http://linuxjournal.com/article.php?sid=4896 .
> >
>
> Ug... why bother? Just buy an SMP system at that point...
Or equally fix the kernel driver to do interrupt mitigation. From
the article that looks like all they have managed to achieve. There
may be a valid argument buried in there for remote DMA as well.
But given in the low contention case the kernel with it's own network
drivers was twice as fast. tcp/ip offload looks to have some serious
weaknesses even for iSCSI. The embedded processor kept better
performance going for just a little while but then it's performance
crashed as well.
Plus there is the general rule. The primary CPU, it's memory, and
it's I/O subsystem improve out of necessity, while IO processors
stagnate, because they can. The only exception to this I have seen
are graphics coprocessors.
Eric
next prev parent reply other threads:[~2002-05-10 18:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 14:48 Tcp/ip offload card driver chen, xiangping
2002-05-10 14:43 ` David S. Miller
2002-05-10 15:11 ` Pedro M. Rodrigues
2002-05-10 15:04 ` David S. Miller
2002-05-10 16:59 ` Jesse Pollard
2002-05-11 22:23 ` Oliver Xymoron
2002-05-10 15:31 ` Jeff Garzik
2002-05-10 15:51 ` Nicholas Harring
2002-05-10 15:49 ` David S. Miller
2002-05-10 16:04 ` Nicholas Harring
2002-05-10 16:09 ` Joel Jaeggli
2002-05-12 0:55 ` john slee
2002-05-12 17:36 ` Mr. James W. Laferriere
2002-05-10 18:36 ` Eric W. Biederman [this message]
2002-05-10 16:02 ` Mark Hahn
2002-05-10 15:12 ` Jeff Garzik
2002-05-10 15:07 ` David S. Miller
2002-05-11 1:53 ` Lincoln Dale
2002-05-12 2:56 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 17:36 Nivedita Singhvi
[not found] <mailman.1021046154.26338.linux-kernel2news@redhat.com>
2002-05-10 17:55 ` Pete Zaitcev
2002-05-10 17:46 ` David S. Miller
2002-05-10 18:39 Nivedita Singhvi
2002-05-10 21:43 Woodruff, Robert J
[not found] <mailman.1021067221.3300.linux-kernel2news@redhat.com>
2002-05-12 2:46 ` Pete Zaitcev
[not found] <Pine.LNX.4.44.0205121335050.14675-100000@filesrv1.baby-dra gons.com>
2002-05-12 22:26 ` Lincoln Dale
2002-05-13 16:17 Woodruff, Robert J
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=m1n0v7zw89.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=chen_xiangping@emc.com \
--cc=davem@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmanuel@myrealbox.com \
/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