Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1393201 > unrolled thread

[PATCH net-next] block/drbd: use nla_put_u64_64bit()

Started byNicolas Dichtel <nicolas.dichtel@6wind.com>
First post2016-05-03 11:00 +0200
Last post2016-05-10 21:30 +0200
Articles 2 on this page of 22 — 4 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  [PATCH net-next] block/drbd: use nla_put_u64_64bit() Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-03 11:00 +0200
    Re: [PATCH net-next] block/drbd: use nla_put_u64_64bit() Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-03 11:30 +0200
      [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-03 11:40 +0200
        Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() Lars Ellenberg <lars.ellenberg@linbit.com> - 2016-05-03 12:10 +0200
          Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-03 14:10 +0200
          Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() David Miller <davem@davemloft.net> - 2016-05-03 18:10 +0200
            Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() Lars Ellenberg <lars.ellenberg@linbit.com> - 2016-05-04 11:10 +0200
              Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-04 14:50 +0200
                Re: [Drbd-dev] [PATCH net-next v2] block/drbd: use  nla_put_u64_64bit() Lars Ellenberg <lars.ellenberg@linbit.com> - 2016-05-04 15:00 +0200
                Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() Eric Dumazet <eric.dumazet@gmail.com> - 2016-05-04 16:30 +0200
                  Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() David Miller <davem@davemloft.net> - 2016-05-04 19:00 +0200
                    Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() Eric Dumazet <eric.dumazet@gmail.com> - 2016-05-04 19:20 +0200
                Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() David Miller <davem@davemloft.net> - 2016-05-04 18:50 +0200
          Re: [PATCH net-next v2] block/drbd: use nla_put_u64_64bit() David Miller <davem@davemloft.net> - 2016-05-03 18:10 +0200
          [PATCH net-next v3] block/drbd: align properly u64 in nl messages Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-09 11:50 +0200
            Re: [PATCH net-next v3] block/drbd: align properly u64 in nl messages Lars Ellenberg <lars.ellenberg@linbit.com> - 2016-05-09 15:20 +0200
              Re: [PATCH net-next v3] block/drbd: align properly u64 in nl messages Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-10 11:20 +0200
                Re: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64 in  nl messages Lars Ellenberg <lars.ellenberg@linbit.com> - 2016-05-10 11:50 +0200
                  Re: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64 in  nl messages Nicolas Dichtel <nicolas.dichtel@6wind.com> - 2016-05-10 12:10 +0200
                  Re: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64  in nl messages David Miller <davem@davemloft.net> - 2016-05-10 17:50 +0200
                    Re: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64 in  nl messages Lars Ellenberg <lars.ellenberg@linbit.com> - 2016-05-10 21:10 +0200
                      Re: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64  in nl messages David Miller <davem@davemloft.net> - 2016-05-10 21:30 +0200

Page 2 of 2 — ← Prev page 1 [2]


#1398421 — Re: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64 in nl messages

FromLars Ellenberg <lars.ellenberg@linbit.com>
Date2016-05-10 21:10 +0200
SubjectRe: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64 in nl messages
Message-ID<rxlcB-uF-3@gated-at.bofh.it>
In reply to#1398256
On Tue, May 10, 2016 at 11:39:49AM -0400, David Miller wrote:
> From: Lars Ellenberg <lars.ellenberg@linbit.com>
> Date: Tue, 10 May 2016 11:40:23 +0200

excuse me for reordering the original:

> Anyways, back to the topic, can you please just relent and come to
> some kind of agreement about the fix for this alignment bug?

I thought we did?  I'm fine with the "v3",
it even carries my signed-of-by.

Whether or not Nicholas wants to prefix those headers with drbd_,
I don't really care.

> This is taking a very long time and patches are just rotting in
> patchwork with no resolution.  Why would 

Nicholas asked how to go about DRBD,
I suggested to use 0 as a padding attribute,
and after taking a detour, he did. All good.


Rest of original:

> > If we introduce a new config option,
> > we have to add it to the config scanner (one line),
> > define min, max, default and scale (four short defines),
> > and add it to the netlink definition here (one line).
> > Done, rest of the code is generated,
> > both on the kernel side,
> > and on the drbd-utils side used to talk to the kernel.
> > We found that to be very convenient.
> 
> But it entirely misses the core design point of netlink.
> 
> Sender and receive _DO NOT_ need to coordinate at all.  That's the
> whole point.  So tightly coupling such coordination is going to run
> you into all kinds of problems.
> 
> When implemented properly, the sender can emit whatever attributes it
> knows about and can generate, and the receive scans the attributes one
> by one and picks out the ones it understands and processes them.
> 
> If you go against this model
> then you have no clean way to

We don't.
We extend (not violate) that model, so the sender *may* indicate
to the recipient that for some particular attribute, the sender would
rather have an "I don't understand this" return than a silent ignore.
And that we can indicate in the definition of the attributes which ones
are required to make a message meaningful.

> extend things whilst allowing existing software to continue working.

*that* is exactly why we use netlink,
and why we do things with it the way we do.
Actually I think what we are doing there is, comparatively, "elegant".
You obviously don't have to agree.

I could discuss this in more detail,
but I assume you are not really interested,
at least not here and now.

Thanks,

    Lars

[toc] | [prev] | [next] | [standalone]


#1398439 — Re: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64 in nl messages

FromDavid Miller <davem@davemloft.net>
Date2016-05-10 21:30 +0200
SubjectRe: [Drbd-dev] [PATCH net-next v3] block/drbd: align properly u64 in nl messages
Message-ID<rxlvY-Gw-15@gated-at.bofh.it>
In reply to#1398421
From: Lars Ellenberg <lars.ellenberg@linbit.com>
Date: Tue, 10 May 2016 21:09:03 +0200

> On Tue, May 10, 2016 at 11:39:49AM -0400, David Miller wrote:
>> From: Lars Ellenberg <lars.ellenberg@linbit.com>
>> Date: Tue, 10 May 2016 11:40:23 +0200
> 
> excuse me for reordering the original:
> 
>> Anyways, back to the topic, can you please just relent and come to
>> some kind of agreement about the fix for this alignment bug?
> 
> I thought we did?  I'm fine with the "v3",
> it even carries my signed-of-by.

My bad, I missed that, I'll apply v3 thanks a lot!

[toc] | [prev] | [standalone]


Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.kernel


csiph-web