From: Evgeniy Polyakov <johnpol@2ka•mipt.ru>
To: Alan Cox <alan@redhat•com>
Cc: Ulrich Drepper <drepper@redhat•com>, netdev <netdev@vger•kernel.org>
Subject: Re: bind and O_NONBLOCK
Date: Sat, 22 Sep 2007 21:40:43 +0400 [thread overview]
Message-ID: <20070922174037.GA22909@2ka.mipt.ru> (raw)
In-Reply-To: <20070922173556.GA26346@devserv.devel.redhat.com>
On Sat, Sep 22, 2007 at 01:35:56PM -0400, Alan Cox (alan@redhat•com) wrote:
> On Sat, Sep 22, 2007 at 08:14:15PM +0400, Evgeniy Polyakov wrote:
> > of operations. There are four ways where bind can fail:
> >
> > 1. unsufficient rights - nothing can help here
> > 2. there is no memory - async binding can not help here too, since it
> > some memory just has to be allocated to save async request
> > somewhere.
> > 3. socket is locked.
> > 4. addres is being bound is in use.
>
> For most protocols yes - but not all. For things like IP specifying O_NDELAY
> is meaningless on a bind it will always complete on the spot as you say
Yes, of course, bind conflict can be handled in different way as Ulrich noted -
from checking bind bucket, to request remote node if address is in use or not.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-09-22 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 5:59 bind and O_NONBLOCK Ulrich Drepper
2007-09-22 16:14 ` Evgeniy Polyakov
2007-09-22 16:21 ` Ulrich Drepper
2007-09-22 16:59 ` Evgeniy Polyakov
2007-09-22 17:11 ` Ulrich Drepper
2007-09-22 17:19 ` Evgeniy Polyakov
2007-09-23 5:58 ` David Miller
2007-09-23 20:43 ` Alan Cox
2007-09-22 17:35 ` Alan Cox
2007-09-22 17:40 ` Evgeniy Polyakov [this message]
2007-09-28 22:56 ` David 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=20070922174037.GA22909@2ka.mipt.ru \
--to=johnpol@2ka$(echo .)mipt.ru \
--cc=alan@redhat$(echo .)com \
--cc=drepper@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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