From: Mandeep Sandhu <Mandeep_Sandhu@infosys.com>
To: dima@s2io.com
Cc: Jeff Garzik <jgarzik@pobox.com>,
"Rajat Jain, Noida" <rajatj@noida.hcltech.com>,
linux-newbie@vger.kernel.org, linux-net@vger.kernel.org,
linux-kernel@vger.kernel.org,
kernelnewbies <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 sendfil e)
Date: Wed, 22 Dec 2004 13:51:58 +0530 [thread overview]
Message-ID: <1103703718.3775.93.camel@samish.india.ascend.com> (raw)
In-Reply-To: <1103658190.7217.121.camel@beastie>
On Wed, 2004-12-22 at 01:13, Dmitry Yusupov wrote:
> indeed :)
> another words if you have modern NIC than you get "zero-copy"(except
> copy_to_user()) for free :)
what does "checksum on rx" mean??? Don't most of the NIC's support
DMA-ing to mem on rx-ing a packet? so what does "zero-copy for free"
mean here?
thanx,
-mandeep
>
> 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
> >
>
>
> --
> Kernelnewbies: Help each other learn about the Linux kernel.
> Archive: http://mail.nl.linux.org/kernelnewbies/
> FAQ: http://kernelnewbies.org/faq/
>
next prev parent reply other threads:[~2004-12-22 8:24 UTC|newest]
Thread overview: 7+ 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
2004-12-22 8:21 ` Mandeep Sandhu [this message]
2004-12-22 15:50 ` zero copy issue while receiving the data (counter part of sendfil e) Martijn van Oosterhout
2004-12-22 16:06 ` John W. Linville
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=1103703718.3775.93.camel@samish.india.ascend.com \
--to=mandeep_sandhu@infosys.com \
--cc=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