Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Erich E. Hoover" <ehoover@mines.edu>
Cc: Linux Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v2] Implement IP_UNICAST_IF socket option.
Date: Fri, 03 Feb 2012 16:43:13 +0100	[thread overview]
Message-ID: <1328283793.2157.33.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <CAEU2+vrMKjLXyABZhi5QrUBA=Fvd4ExgMxjD+T376AZW1SRd8A@mail.gmail.com>

Le vendredi 03 février 2012 à 08:21 -0700, Erich E. Hoover a écrit :
> On Fri, Feb 3, 2012 at 3:01 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> > ...
> > BTW, do we really want the htonl() thing, and force device indexes in
> > 2^24 range ? This seems odd anyway.
> > ...
> 
> I can easily perform both of these steps in Wine.  The 2^24 limitation
> in particular seems artificial, and especially silly to add to the
> kernel if it will change the fundamental range of the indices.  With
> regard to htonl(), David Miller indicated that the API should match
> what other systems use (a 32-bit network byte order word), though he
> may not have meant his comment that specifically.  I can see the
> merits of doing it both ways and I'm not particularly attached to
> either one.

I have no strong feeling, I only wanted to point out our current device
indexes range is [1 .. (2^31 - 1) ]

  reply	other threads:[~2012-02-03 15:43 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 [this message]
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

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=1328283793.2157.33.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
    --to=eric.dumazet@gmail.com \
    --cc=ehoover@mines.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox