From: J. Bruce Fields <bfields@fieldses.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH 2/3] NLM per-ip grace period - core
Date: Tue, 29 Jan 2008 12:21:01 -0500 [thread overview]
Message-ID: <20080129172101.GA28032@fieldses.org> (raw)
In-Reply-To: <514B944F-02FC-4164-BFDA-209361F4BD25@oracle.com>
On Tue, Jan 29, 2008 at 11:33:08AM -0500, Chuck Lever wrote:
> On Jan 28, 2008, at 9:56 PM, J. Bruce Fields wrote:
>> Also, is that the right choice of types? Maybe we should just use
>> struct in6_addr?
>
> I agree with Bruce -- just use in_addr, and leave out the unused IPv6
> stuff for now.
>
> In some places, we just replace in_addr with in6_addr and simply map
> IPv4 to IPv6 addresses, rather than setting up a union.
>
> If the address is used as a hash and never displayed, using a mapped
> IPv4 address is sufficient, and keeps things simple.
>
>> +
>> int
>> nlmsvc_failover_setgrace(void *server_ip, int ip_size)
>
> Should this be
>
> int nlmsvc_failover_setgrace(const struct in_addr *server_ip)
>
> for now, and later we can change it to use in6_addr instead?
I could go either way, If it'd be just as easy to use in6_addr's
internally everywhere from the start, that'd be great, and then it'll be
easy enough to tack the ipv6 parsing onto the interfaces later.
But I'd leave that to Wendy's judgement for now--I think it's reasonable
to keep it ipv4 only for now if that keeps the initial implementation
simpler.
(Just drop the union and use in_addr or in6_addr as opposed to the
home-grown types.)
--b.
next prev parent reply other threads:[~2008-01-29 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 5:17 [Cluster-devel] [PATCH 2/3] NLM per-ip grace period - core Wendy Cheng
2008-01-29 2:56 ` [Cluster-devel] " J. Bruce Fields
[not found] ` <514B944F-02FC-4164-BFDA-209361F4BD25@oracle.com>
2008-01-29 17:10 ` Wendy Cheng
2008-01-29 17:21 ` J. Bruce Fields [this message]
2008-01-30 0:14 ` J. Bruce Fields
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=20080129172101.GA28032@fieldses.org \
--to=bfields@fieldses.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).