public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Subba Rao <subba9@home.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Half Duplex and Zero Copy IP
Date: Fri, 10 Aug 2001 11:36:06 -0700	[thread overview]
Message-ID: <3B742996.3F2C8DEC@zip.com.au> (raw)
In-Reply-To: <20010810095313.A6219@home.com>

Subba Rao wrote:
> 
> Hello,
> 
> I have 2 3Com NICs on my system. They are 3c905C Tornado PCI cards.
> The drivers are compiled into the kernel (Slackware 8.0 with kernel 2.4.7).
> 
> One of the interfaces will be used as a sniffer interface (without IP address)
> and a very high traffic pipes. I do not wish to loose any packets coming to this
> interface. Is it better if I initialize the interface in HALF DUPLEX mode? If yes,
> how do I set the card to HALF DUPLEX mode? How can I find out the HW (NIC) settings
> on the system?

No, this will provide no benefit.

> Another question about 3Com NICs, do they perform zero-copy IP?

Linux's zerocopy infrastructure allows the sendfile() system call
to save a copy with NICs which have hardware checksumming and
scatter/gather.  3c905C is one such NIC.  Kernel is not generally
"zero copy", but large savings are available in certain situations.
NFS packet reassembly benefits from 905C's as well.

> I read that the performance improves a lot WITHOUT zero-copy IP.

Not right.  Where did you read that?

-

  reply	other threads:[~2001-08-10 18:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-10  9:53 Half Duplex and Zero Copy IP Subba Rao
2001-08-10 18:36 ` Andrew Morton [this message]
2001-08-11  7:59   ` Subba Rao
2001-08-10 18:46 ` Andi Kleen
2001-08-10 23:50   ` Jamie Lokier
2001-08-11  0:00     ` Andi Kleen

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=3B742996.3F2C8DEC@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=subba9@home.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