From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: RFC: Redirect-Device
Date: Thu, 31 Mar 2005 14:04:11 -0800 [thread overview]
Message-ID: <424C73DB.2090501@candelatech.com> (raw)
In-Reply-To: <20050331135229.432afff3.davem@davemloft.net>
David S. Miller wrote:
> On Thu, 31 Mar 2005 13:45:38 -0800
> Ben Greear <greearb@candelatech.com> wrote:
>
>
>>> Adding new ioctl's are very frowned on
>>
>>Bummer. I want these as well, makes programatic reading of the information
>>much easier than trying to parse some proc file. I will look into what it
>>takes to make them compat with 64-bit as DaveM suggested.
>
>
> You could extend and use ethtool. That is what it's there for.
The IOCTLs I need are very specific and will only be used for
the redirect module. I don't think it would be worth adding
a function pointer to the ethtool-ops, but if that is what you
prefer I can do so.
With regard to the compat: I did a quick search for 'vlan' in that
file, thinking I'd mimic whatever was done for the .1q module. There
is no mention of vlan anywhere in there. Does that mean that so long
as I don't use pointers, strictly define my data types (u32, etc),
and make sure the ioctl structs are padded to 32-bit (or maybe 64-bit?)
boundaries, I don't need any 64-bit compat code?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-03-31 22:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 20:41 RFC: Redirect-Device Ben Greear
2005-03-31 21:02 ` David S. Miller
2005-03-31 21:05 ` Stephen Hemminger
2005-03-31 21:45 ` Ben Greear
2005-03-31 21:52 ` David S. Miller
2005-03-31 22:04 ` Ben Greear [this message]
2005-03-31 22:21 ` David S. Miller
2005-03-31 22:05 ` Stephen Hemminger
2005-03-31 22:26 ` Ben Greear
2005-03-31 22:33 ` David S. Miller
2005-03-31 22:42 ` Ben Greear
2005-03-31 22:43 ` David S. Miller
2005-03-31 21:13 ` jamal
2005-03-31 21:26 ` Ben Greear
2005-03-31 21:53 ` jamal
2005-03-31 22:22 ` Ben Greear
2005-03-31 22:35 ` David S. Miller
2005-03-31 22:54 ` Ben Greear
2005-03-31 23:26 ` jamal
2005-03-31 23:56 ` Ben Greear
2005-04-01 0:53 ` jamal
2005-04-01 9:01 ` bert hubert
2005-04-01 16:58 ` Ben Greear
2005-03-31 22:46 ` Thomas Graf
2005-03-31 23:00 ` Ben Greear
2005-03-31 23:20 ` jamal
2005-03-31 23:35 ` Ben Greear
2005-03-31 23:46 ` jamal
2005-04-02 8:41 ` Meelis Roos
2005-04-02 21:08 ` jamal
2005-04-01 5:03 ` Pekka Savola
2005-04-01 5:27 ` Ben Greear
2005-04-01 9:28 ` Pekka Savola
2005-04-01 16:29 ` Ben Greear
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=424C73DB.2090501@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).