All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Ulrich Drepper <drepper@redhat.com>
Cc: netdev <netdev@vger.kernel.org>, Alan Cox <alan@redhat.com>
Subject: Re: bind and O_NONBLOCK
Date: Sat, 22 Sep 2007 20:59:38 +0400	[thread overview]
Message-ID: <20070922165938.GA11234@2ka.mipt.ru> (raw)
In-Reply-To: <46F540F2.1090109@redhat.com>

On Sat, Sep 22, 2007 at 09:21:06AM -0700, Ulrich Drepper (drepper@redhat.com) wrote:
> Evgeniy Polyakov wrote:
> > So, did I understand you correctly, that you want to introduce network
> > AIO here? (for example on behalf of work queue or something else?)
> 
> See Alan's mail.  All this was his proposal, I just got it accepted
> upstream.
> 
> The problem to solve is if you have a distributed network port set.
> Apparently NetBIOS has it but I could also imagine this to be useful in
> cluster implementations which have to appear as one machine.  In this
> case, before binding to a given port, you have to make sure no other
> machine already handles this port.

Yes, to handle bind conflict in some or another way.
Could you point to the original Alan's proposal, I only found short note
(as in you original mail) at opengroup.org and failed to correctly
googlify it in the web.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2007-09-22 17:00 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 [this message]
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
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=20070922165938.GA11234@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=alan@redhat.com \
    --cc=drepper@redhat.com \
    --cc=netdev@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.