public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: ranjith kumar <ranjithproxy@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: how to read one udp packet with more than one recvfrom() calls?
Date: Mon, 08 Nov 2010 10:31:39 -0800	[thread overview]
Message-ID: <4CD8420B.8050000@hp.com> (raw)
In-Reply-To: <AANLkTi=40758wF4Z6GDfm809miA-hnCnSQdwA9bALX0+@mail.gmail.com>

ranjith kumar wrote:
> Hi,
> 
> I  have implemented client and server programs using udp
> protocol(files are attached). UDP packet size is 500bytes.
> 
> I want to read these 500bytes in two calls to recvfrom(). First time
> reading 100bytes and second time 400bytes.
> How to do this?

You can't. Certainly not in antyhing remotely portable.  Receipt of a UDP 
datagram is a one-shot proposition - the bytes from the UDP datagram that do not 
fit in the buffer(s) provided in the receive call are discarded.  You might look 
into readv() or recvmsg() if you want to get bytes placed into different buffers.

> When I tried to change the third argument of recvfrom(size_t len),
> from 500 to 100, first 100bytes are read correctly.
> But when I call recvfrom() second time with len=400, it is reading the
> first 400bytes of "next udp packet".
> Why? Isn't it possible to read one udp packet in two calls to
> recvfrom()/read()????

SOCK_DGRAM+UDP provides datagram semantics, not byte-stream semantics.

rick jones

  parent reply	other threads:[~2010-11-08 18:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  7:08 how to read one udp packet with more than one recvfrom() calls? ranjith kumar
2010-11-08  7:12 ` Changli Gao
2010-11-08  7:51 ` Michael Tokarev
2010-11-08 18:31 ` Rick Jones [this message]
2010-11-09  5:35 ` Varun Chandramohan

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=4CD8420B.8050000@hp.com \
    --to=rick.jones2@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranjithproxy@gmail.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