netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: David Miller <davem@davemloft.net>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"gospo@redhat.com" <gospo@redhat.com>
Subject: Re: [net-next-2.6 PATCH v2 1/3] ethtool: Introduce n-tuple filter programming support
Date: Thu, 04 Feb 2010 15:07:50 -0800	[thread overview]
Message-ID: <1265324870.2780.16.camel@localhost> (raw)
In-Reply-To: <4B6B5077.9070005@garzik.org>

On Thu, 2010-02-04 at 14:55 -0800, Jeff Garzik wrote:
> On 02/04/2010 05:52 PM, Peter P Waskiewicz Jr wrote:
> > On Thu, 2010-02-04 at 14:34 -0800, Jeff Garzik wrote:
> >> On 02/04/2010 04:26 PM, Waskiewicz Jr, Peter P wrote:
> >>> On Thu, 4 Feb 2010, David Miller wrote:
> >>>
> >>>> From: Jeff Kirsher<jeffrey.t.kirsher@intel.com>
> >>>> Date: Wed, 03 Feb 2010 23:48:13 -0800
> >>>>
> >>>>> +#define ETHTOOL_RXNTUPLE_ACTION_DROP -1
> >>>>> +	struct list_head list;
> >>>>> +};
> >>>>
> >>>> You can't do this.
> >>>>
> >>>> You put the list_head here in the kernel header, which BTW can
> >>>> be used by userspace too, and then you elide it in the
> >>>> ethtool utility copy of the header.
> >>>>
> >>>> Use an encapsulator if you must inside of the kernel, but keep the
> >>>> userspace visible data structure clean of RCU and list_head
> >>>> kernel datastructures.
> >>>
> >>> Ok.  I'll respin this asap.  Thanks for the quick review Dave.
> >>
> >> Great.  I'll look for the updated userspace patch, too, and put it into
> >> the ethtool-2.6.34 pile (ie. ethtool-net-next).
> >>
> >
> > I didn't plan on respinning the userspace side.  I put a container
> > wrapped around the flow_spec struct to do the list management in the
> > kernel.  This shouldn't need a change to userspace.
> 
> Well, I figured there would be some trivial tweaks and patch offsets, 
> because we want to keep the kernel ethtool.h and userspace 
> ethtool-copy.h headers in sync.
> 
> Either way, no big deal.  I'll make sure net-next and ethtool match up, 
> after your userspace patch is applied, one way or the other.

Well, my "fixing" of the kernel side will make the structures align now.

Thanks for staying on top of this though.  :-)

-PJ


      reply	other threads:[~2010-02-04 23:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-04  7:48 [net-next-2.6 PATCH v2 1/3] ethtool: Introduce n-tuple filter programming support Jeff Kirsher
2010-02-04  7:48 ` [net-next-2.6 PATCH v2 2/3] ixgbe: Add support for the new ethtool n-tuple programming interface Jeff Kirsher
2010-02-04  7:48 ` [net-next-2.6 PATCH v2 3/3] ixgbe: Bump driver version up Jeff Kirsher
2010-02-04 17:18 ` [net-next-2.6 PATCH v2 1/3] ethtool: Introduce n-tuple filter programming support David Miller
2010-02-04 21:26   ` Waskiewicz Jr, Peter P
2010-02-04 22:34     ` Jeff Garzik
2010-02-04 22:52       ` Peter P Waskiewicz Jr
2010-02-04 22:55         ` Jeff Garzik
2010-02-04 23:07           ` Peter P Waskiewicz Jr [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=1265324870.2780.16.camel@localhost \
    --to=peter.p.waskiewicz.jr@intel.com \
    --cc=davem@davemloft.net \
    --cc=gospo@redhat.com \
    --cc=jeff@garzik.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --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).