All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Peter Staubach <staubach@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Can you specify a local IP or Interface to be used on a per NFS mount basis?
Date: Fri, 20 Jan 2006 09:11:43 -0800	[thread overview]
Message-ID: <43D119CF.9040805@candelatech.com> (raw)
In-Reply-To: <43D0EB32.5050909@redhat.com>

Peter Staubach wrote:

> These changes are very IPv4 specific.  Perhaps they could be constructed 
> in a
> bit more IP version agnostic fashion?  IPv6 is coming as well as other 
> transport
> choices, not all of whose addresses will fit into 32 bits.

Sure..it'd be best to pass in a generic structure that can hold
ipv4 or v6 address and port.  But, I have no setup to test ipv6,
don't need to specify the port, and this patch can't go in anyway
because Trond doesn't want to change the binary structure....

If we go to a text base API, could just pass it in as "IP:port"
and let the kernel parsing logic decide if it's IPv4, v6 or something
else...  Of course, it sure is nice to leave all the parsing logic
in user-space, but then you're back to a binary API...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


      reply	other threads:[~2006-01-20 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18 23:10 Can you specify a local IP or Interface to be used on a per NFS mount basis? Ben Greear
2006-01-19  0:48 ` Trond Myklebust
2006-01-19  2:21   ` Ben Greear
2006-01-19  2:29     ` David S. Miller
2006-01-19  3:24     ` Trond Myklebust
2006-01-19  3:28       ` Ben Greear
2006-01-19  4:24         ` Trond Myklebust
2006-01-20  4:26           ` Ben Greear
2006-01-20 13:52             ` Peter Staubach
2006-01-20 17:11               ` Ben Greear [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=43D119CF.9040805@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=staubach@redhat.com \
    --cc=trond.myklebust@fys.uio.no \
    /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.