From: Jiri Kortus <sumix-a4qEbw8STSk@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: IPv6 support in pNFS
Date: Fri, 14 May 2010 19:35:30 +0200 [thread overview]
Message-ID: <4BED89E2.8070903@atlas.cz> (raw)
Hi,
I'm sorry to flood the mailing list by repeating my question several
times - I've already asked whether someone would be so kind as to tell
me something about the situation of IPv6 support in pNFS. Just anything
related to it would be appreciated very much since nobody gave me an
answer (except Boaz Harrosh who wrote me about the IPv6 absence in OSD
target). I'd like to know whether there's any support for IPv6
(concerning all of the layouts available), if yes what are the issues
with that, if not when the implementation is planned to start etc. I did
google that a lot before asking but haven't found anything. Thanks very
much in advance.
Best regards,
Jiri Kortus
next reply other threads:[~2010-05-14 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-14 17:35 Jiri Kortus [this message]
[not found] ` <4BED89E2.8070903-a4qEbw8STSk@public.gmane.org>
2010-05-14 17:49 ` IPv6 support in pNFS Chuck Lever
2010-05-14 17:55 ` Andy Adamson
2010-05-16 13:42 ` Jiri Kortus
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=4BED89E2.8070903@atlas.cz \
--to=sumix-a4qebw8stsk@public.gmane.org \
--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 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).