From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Graf <tgraf@suug.ch>
Cc: netdev <netdev@vger.kernel.org>, davem <davem@davemloft.net>
Subject: Re: [RFC] genetlink custom attribute type
Date: Thu, 14 Sep 2006 11:21:44 +0200 [thread overview]
Message-ID: <1158225704.2936.27.camel@ux156> (raw)
In-Reply-To: <20060914081409.GB18349@postel.suug.ch>
On Thu, 2006-09-14 at 10:14 +0200, Thomas Graf wrote:
> Looks good, we have to watch the size of struct nla_policy though.
> This bumps the size from 4 bytes to 16 bytes on 64bit architectures
> which might become a problem since we always use ATTR_MAX sized
> arrays.
Yes, I'm aware of that, but I couldn't think of a way to handle it well.
I thought about using a second array containing just the check
functions, and then (ab)using `len' to index into it but that didn't
seem clean enough.
Can you think of something better?
johannes
next prev parent reply other threads:[~2006-09-14 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 7:44 [RFC] genetlink custom attribute type Johannes Berg
2006-09-14 8:14 ` Thomas Graf
2006-09-14 9:21 ` Johannes Berg [this message]
2006-09-20 6:24 ` Thomas Graf
2006-09-25 14:58 ` Johannes Berg
2006-09-25 23:48 ` David Miller
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=1158225704.2936.27.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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