From: Santwona.Behera@Sun.COM
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, gkernel-commit@lists.sourceforge.net,
Matheos.Worku@Sun.COM, jeff@garzik.org, Mehdi.Bonyadi@Sun.COM
Subject: Re: [gkernel-commit] [PATCH 2/3] [kernel] Add support for RX packet classification in a network device
Date: Fri, 20 Feb 2009 09:19:29 -0800 [thread overview]
Message-ID: <499EE621.6000605@Sun.COM> (raw)
In-Reply-To: <20090220.005532.166859047.davem@davemloft.net>
Hi Dave,
I actually did make the changes and compile with sparse (without any
warnings, at least for the access of these fields), but I haven't had
the time to test it yet, which is why I did not post the new patches.
Thanks for taking care of it.
--santwona
On 02/20/09 12:55 AM, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Tue, 17 Feb 2009 20:28:38 -0800 (PST)
>
>> From: Santwona.Behera@Sun.COM
>> Date: Mon, 16 Feb 2009 09:17:23 -0800
>>
>>> -struct ethtool_rxnfc {
>>> - __u32 cmd;
>>> +/* The following structures are for supporting RX network flow
>>> + * classification configuration. Note, all multibyte fields, e.g.,
>>> + * ip4src, ip4dst, psrc, pdst, spi, etc. are expected to be in network
>>> + * byte order.
>>> + */
>>> +struct ethtool_tcpip4_spec {
>>> + __u32 ip4src;
>>> + __u32 ip4dst;
>>> + __u16 psrc;
>>> + __u16 pdst;
>>> + __u8 tos;
>>> +};
>> We have specific types for this, "__be32" et al.
>
> Nevermind, you obviously don't have time to get to this quickly
> so I'll take care of it while checking this stuff in...
>
prev parent reply other threads:[~2009-02-20 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 17:17 [PATCH 2/3] [kernel] Add support for RX packet classification in a network device Santwona.Behera
2009-02-18 4:28 ` David Miller
2009-02-18 6:07 ` Harvey Harrison
2009-02-20 8:55 ` David Miller
2009-02-20 17:19 ` Santwona.Behera [this message]
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=499EE621.6000605@Sun.COM \
--to=santwona.behera@sun.com \
--cc=Matheos.Worku@Sun.COM \
--cc=Mehdi.Bonyadi@Sun.COM \
--cc=davem@davemloft.net \
--cc=gkernel-commit@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=netdev@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).