All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman@suse.de>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: IPv6 support
Date: Mon, 02 Nov 2009 13:50:21 +0530	[thread overview]
Message-ID: <4AEE9645.6010503@suse.de> (raw)

Hi Chuck et al,

Thanks for all the excellent work on IPv6 support. There have been
considerable amount of development that has been happening recently.
However, it's not very clear what are the missing pieces or open
problems (if any).

>From what I understand, the current status is (CMIW):

+ kernel support
  - client side and server (kernel pieces) are almost there and the
    missing pieces are expected to get in by 2.6.32.
+ userspace support
  - nfsd support has already been added but disabled temporarily till
    we get statd and mountd IPv6 aware.
  - making statd IPv6 aware is currently under development/review.
  - mount.nfs changes - done?
  - rpc.mountd, exportfs changes - TBD.

Is the above information correct? How far we are from getting full IPv6
support?


Thanks,

-- 
Suresh Jayaraman

             reply	other threads:[~2009-11-02  8:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  8:20 Suresh Jayaraman [this message]
2009-11-02 16:40 ` IPv6 support Chuck Lever
2009-11-02 20:43   ` Jeff Layton
2009-11-05 11:49   ` Suresh Jayaraman
2009-11-05 14:41     ` Chuck Lever
2009-11-19 15:17   ` IPv6 support: dreaming of Ivan Shmakov
     [not found]     ` <87hbsqbl3d.fsf_-_-Hr8DDCuc/25fzK4uoAgqGcYP0srqJqIshoJSb6RVeLg@public.gmane.org>
2009-11-19 16:05       ` Chuck Lever
2009-11-19 16:18   ` IPv6 support Ivan Shmakov
  -- strict thread matches above, loose matches on Subject: below --
2011-01-18 13:40 Mika Liljeberg
2021-02-02  0:28 IPv6 Support Raymond Yeung

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=4AEE9645.6010503@suse.de \
    --to=sjayaraman@suse.de \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@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.