public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: "Hurwitz Justin W." <hurwitz@lanl.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How many copies to get from NIC RX to user read()?
Date: Wed, 10 Jul 2002 14:27:01 -0700	[thread overview]
Message-ID: <1026336421.3d2ca6a50d35b@imap.linux.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207101509240.17835-100000@alvie-mail.lanl.gov>


> So, to make sure I have this right:
> 
> When the data is processed from the NIC
>   tcp_rcv_established() is called in processing it
>     if a user process is waiting on the socket
>       iovec copy data to the user
>     else
>       copy it to receive_queue or backlog_queue

well, we append the skb to the tail of the queue.
this is not a copy operation. (just a few instructions).

> When the user tries read (in any way) a socket
>   iovec copy from receive_queue or backlog_queue
> 
> 
> E.g., if the user is ready for the data, dump it straight from
> SKBs. Else, 
> don't waste SKBs on a lazy (or busy) user and copy the data to a
> queue.

yep.

> If this is right, I'm happy :) If it's wrong, please correct. 
> 
> Thx,
> --Gus

I should add that my reading of the code is hardly
authoritative :). caveat emptor...

thanks,
Nivedita




  reply	other threads:[~2002-07-10 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-10 15:52 How many copies to get from NIC RX to user read()? niv
2002-07-10 21:15 ` Hurwitz Justin W.
2002-07-10 21:27   ` Nivedita Singhvi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-09 22:29 Hurwitz Justin W.
2002-07-09 23:11 ` Alan Cox
2002-07-10  8:29 ` Matti Aarnio
2002-07-11  2:12   ` David S. 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=1026336421.3d2ca6a50d35b@imap.linux.ibm.com \
    --to=niv@us.ibm.com \
    --cc=hurwitz@lanl.gov \
    --cc=linux-kernel@vger.kernel.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