All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: 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: Wed, 18 Jan 2006 19:28:40 -0800	[thread overview]
Message-ID: <43CF0768.60703@candelatech.com> (raw)
In-Reply-To: <1137641084.8864.3.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> On Wed, 2006-01-18 at 18:21 -0800, Ben Greear wrote:
> 
> 
>>>NFS doesn't know anything about ip packet routing. That is a networking
>>>issue.
>>
>>When a socket is created, you can optionally bind to local IP, interface and/or
>>IP-Port.  Somewhere, NFS is opening a socket I assume?  So, is there a way to
>>ask it to bind?
> 
> 
> 
> As David said, the place to fix it is in xs_bindresvport(), but there is
> no support for passing this sort of information through the current NFS
> binary mount structure. You would have to hack that up yourself.

I can think of some horrible hacks to grab info out of a text file based
on the mount point or some other available info...but if I actually
attempted to do it right..would you consider the patch for kernel
inclusion?  Is it OK to modify the binary mount structure?

Ben

> 
> Cheers,
>   Trond
> 


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


  reply	other threads:[~2006-01-19  3:28 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 [this message]
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

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=43CF0768.60703@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.