public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: Chris Wright <chris@wirex.com>
Cc: Ben Greear <greearb@candelatech.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 14:05:31 -0500	[thread overview]
Message-ID: <3C15077B.6AD2693E@nortelnetworks.com> (raw)
In-Reply-To: <3C145359.3090401@candelatech.com> <20011209233349.C27109@figure1.int.wirex.com>

Chris Wright 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?

Are you sure about that? UDP has a 16-bit field for the length.  Thus the
standard technically allows for packet sizes (including header) of up to 2^16
(roughly 65K) bytes.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10  
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com

  parent reply	other threads:[~2001-12-10 19:05 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
2001-12-10 19:05   ` Christopher Friesen [this message]
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=3C15077B.6AD2693E@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=chris@wirex.com \
    --cc=greearb@candelatech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox