netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: xiaoclu@gmail.com
Cc: ehoover@mines.edu, eric.dumazet@gmail.com,
	netdev@vger.kernel.org, shawn.lu@ericssion.com
Subject: Re: [PATCH v2] Implement IP_UNICAST_IF socket option.
Date: Thu, 02 Feb 2012 20:50:44 -0500 (EST)	[thread overview]
Message-ID: <20120202.205044.565511915004327213.davem@davemloft.net> (raw)
In-Reply-To: <CAOdseAOsGOD2bxOwQLZPq6KhL5xN9J81=d1tQWEULDZwxD9UxA@mail.gmail.com>

From: Xiaochun Lu <xiaoclu@gmail.com>
Date: Thu, 2 Feb 2012 17:19:11 -0800

> Hi, Erich E. Hoover:
> 
> Can you give more detail on why we need invent another binding to
> device option in your patch log?  Why SO_BINDTODEVICE or IP_PKTINFO
> can't server your need?

Windows apps via wine will make use of this, and you can't just use
bind()'ing or IP_PKTINFO because the former doesn't work on broadcast
addreses and the latter might be used by the wine application at the
same time as IP_UNICAST_IF.

He explained this fully in his previous patch discussion, DO NOT repeat
this whole discussion it's a waste of time.

      parent reply	other threads:[~2012-02-03  1:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02 21:36 [PATCH v2] Implement IP_UNICAST_IF socket option Erich E. Hoover
2012-02-02 21:57 ` Eric Dumazet
2012-02-02 22:29   ` Erich E. Hoover
2012-02-02 22:45     ` Eric Dumazet
2012-02-03  1:22       ` Erich E. Hoover
2012-02-03  1:51         ` David Miller
2012-02-03 10:01         ` Eric Dumazet
2012-02-03 15:21           ` Erich E. Hoover
2012-02-03 15:43             ` Eric Dumazet
2012-02-03  1:19     ` Xiaochun Lu
2012-02-03  1:38       ` Erich E. Hoover
2012-02-03  2:15         ` Xiaochun Lu
2012-02-03  1:50       ` David Miller [this message]

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=20120202.205044.565511915004327213.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ehoover@mines.edu \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=shawn.lu@ericssion.com \
    --cc=xiaoclu@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;
as well as URLs for NNTP newsgroup(s).