All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: Chris Wright <chris@wirex.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: question on select:  How big can the empty buffer space be before select returns ready-to-write?
Date: Mon, 10 Dec 2001 09:41:49 -0700	[thread overview]
Message-ID: <3C14E5CD.9050906@candelatech.com> (raw)
In-Reply-To: <E16DLx4-0001Ds-00@the-village.bc.nu>



Alan Cox wrote:

>>* Ben Greear (greearb@candelatech.com) wrote:
>>
>>>For instance, it appears that select will return that a socket is
>>>writable when there is, say 8k of buffer space in it.  However, if
>>>I'm sending 32k UDP packets, this still causes me to drop packets
>>>due to a lack of resources...
>>>
>>udp has a fixed 8k max payload. did you try breaking up your packets?
>>
> 
> UDP has a 64K - headers max payload. 


Yes, and I am writing code to specifically try out large UDP
packet sizes, so limiting myself to a certain size is not at
all useful in this case....

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  reply	other threads:[~2001-12-10 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10  6:16 question on select: How big can the empty buffer space be before select returns ready-to-write? Ben Greear
2001-12-10  7:33 ` Chris Wright
2001-12-10  8:38   ` Alan Cox
2001-12-10 16:41     ` Ben Greear [this message]
2001-12-10 19:05   ` Christopher Friesen
2001-12-10 21:46     ` Chris Wright

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=3C14E5CD.9050906@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=chris@wirex.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.