public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Yusupov <dima@s2io.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Rajat Jain, Noida" <rajatj@noida.hcltech.com>,
	linux-newbie@vger.kernel.org, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org,
	"Sanjay Kumar, Noida" <sanjayku@hcltech.com>,
	"Deepak Kumar Gupta, Noida" <dkumar@hcltech.com>
Subject: Re: zero copy issue while receiving the data (counter part of sen dfil e)
Date: Tue, 21 Dec 2004 11:43:10 -0800	[thread overview]
Message-ID: <1103658190.7217.121.camel@beastie> (raw)
In-Reply-To: <41C879CB.3040600@pobox.com>

indeed :)
another words if you have modern NIC than you get "zero-copy"(except
copy_to_user()) for free :)

Regards,
Dima

On Tue, 2004-12-21 at 14:30 -0500, Jeff Garzik wrote:
> Dmitry Yusupov wrote:
> > Rajat,
> > 
> > small correction, if NIC supports DMA operation on receive, than no
> > extra copy required. Therefore sock_recvmsg() and tcp_read_sock
> 
> large correction:  if NIC supports _checksum_ on receive, then no extra 
> copy is required.
> 
> 	Jeff
> 


  reply	other threads:[~2004-12-21 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21 16:35 zero copy issue while receiving the data (counter part of sen dfil e) Rajat  Jain, Noida
2004-12-21 17:22 ` Dmitry Yusupov
2004-12-21 19:30   ` Jeff Garzik
2004-12-21 19:43     ` Dmitry Yusupov [this message]
2004-12-22  8:21       ` zero copy issue while receiving the data (counter part of sendfil e) Mandeep Sandhu
2004-12-22 15:50         ` Martijn van Oosterhout
2004-12-22 16:06           ` John W. Linville
  -- strict thread matches above, loose matches on Subject: below --
2004-12-17 16:24 zero copy issue while receiving the data (counter part of sen dfil e) Rajat  Jain, Noida
2004-12-17 17:31 ` Dmitry Yusupov

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=1103658190.7217.121.camel@beastie \
    --to=dima@s2io.com \
    --cc=dkumar@hcltech.com \
    --cc=jgarzik@pobox.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=rajatj@noida.hcltech.com \
    --cc=sanjayku@hcltech.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