All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Shirley Ma <mashirle@us.ibm.com>,
	David Miller <davem@davemloft.net>,
	Eric Dumazet <eric.dumazet@gmail.com>,
	Avi Kivity <avi@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
	netdev@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5 2/6 net-next] netdevice.h: Add zero-copy flag in netdevice
Date: Tue, 17 May 2011 00:14:59 +0300	[thread overview]
Message-ID: <20110516211459.GE18148@redhat.com> (raw)
In-Reply-To: <1305575253.2885.28.camel@bwh-desktop>

On Mon, May 16, 2011 at 08:47:33PM +0100, Ben Hutchings wrote:
> On Mon, 2011-05-16 at 12:38 -0700, Shirley Ma wrote:
> > On Mon, 2011-05-16 at 20:35 +0100, Ben Hutchings wrote:
> > > Sorry, bit 31 is taken.  You get the job of turning features into a
> > > wider bitmap.
> > 
> > :) will do it.
> 
> Bear in mind that feature masks are manipulated in many different
> places.  This is not a simple task.
> 
> See previous discussion at:
> http://thread.gmane.org/gmane.linux.network/193284
> and especially:
> http://thread.gmane.org/gmane.linux.network/193284/focus=193332
> 
> Ben.


IIUC, what is suggested above is something like:

typedef struct net_features {
} net_features_t;

and then

   void netdev_set_feature(net_features_t *net_features, int feature);
   void netdev_clear_feature(net_features_t *net_features, int feature);
   bool netdev_test_feature(net_features_t *net_features, int feature);


I think this might be the easiest way as compiler will catch any direct uses.
It can then be split up nicely.

It looks a bit different from what Dave suggested but I think it's
close enough?

we could also have wrappers that set/clear/test many features to replace
uses of A|B|C that are pretty common.

   static inline void netdev_set_features(net_features_t *net_features, int nfeatures, int *features)
   {
	int i;
	for (i = 0; i < nfeatures; ++i)
		netdev_set_feature(net_features, features[i]);
   }
   void netdev_clear_features(net_features_t *net_features, int nfeatures, int *features)
   {
	int i;
	for (i = 0; i < nfeatures; ++i)
		netdev_clear_feature(net_features, features[i]);
   }
   bool netdev_test_features(net_features_t *net_features, int nfeatures, int *features)
   {
	int i;
	for (i = 0; i < nfeatures; ++i)
		if (netdev_test_feature(net_features, features[i]))
			return true;
	return false;
   }

and possibly macros that get arrays of constants:

#define NETDEV_SET_FEATURES(net_features, feature_array) do { \
	int __NETDEV_SET_FEATURES_F[] = feature_array;
	netdev_set_feature((net_features), \
		ARRAY_SIZE(__NETDEV_SET_FEATURES_F), __NETDEV_SET_FEATURES_F);
} while (0)

etc.

> -- 
> Ben Hutchings, Senior Software Engineer, Solarflare
> Not speaking for my employer; that's the marketing department's job.
> They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2011-05-16 21:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 19:28 [PATCH V5 2/6 net-next] netdevice.h: Add zero-copy flag in netdevice Shirley Ma
2011-05-16 19:35 ` Ben Hutchings
2011-05-16 19:38   ` Shirley Ma
2011-05-16 19:47     ` Ben Hutchings
2011-05-16 21:14       ` Michael S. Tsirkin [this message]
2011-05-16 23:32         ` Shirley Ma
2011-05-17  6:21           ` Michael S. Tsirkin
2011-05-17 20:53             ` Shirley Ma
2011-05-17 21:48           ` Michał Mirosław
2011-05-17 22:28             ` Shirley Ma
2011-05-17 22:58               ` Michał Mirosław
2011-05-17 23:44                 ` Shirley Ma
2011-05-18  9:06                   ` Michał Mirosław
2011-05-18 10:38               ` Michael S. Tsirkin
2011-05-18 11:10                 ` Michał Mirosław
2011-05-18 11:17                   ` Michael S. Tsirkin
2011-05-18 11:40                     ` Michał Mirosław
2011-05-18 11:47                       ` Michael S. Tsirkin
2011-05-18 14:38                       ` Shirley Ma
2011-05-18 15:47                         ` Michael S. Tsirkin
2011-05-18 16:07                           ` Shirley Ma
2011-05-18 16:36                             ` Michael S. Tsirkin
2011-05-18 16:45                               ` Shirley Ma
2011-05-18 16:51                                 ` Michael S. Tsirkin
2011-05-18 17:00                                   ` Shirley Ma
2011-05-19 19:42                                     ` Shirley Ma
2011-05-19 23:41                                       ` Michael S. Tsirkin
2011-05-25 22:49                                         ` Shirley Ma
2011-05-26  8:49                                           ` Michael S. Tsirkin
2011-05-26 15:27                                             ` Shirley Ma
2011-05-26 19:11                                             ` Shirley Ma
2011-05-18 16:02                         ` Shirley Ma
2011-05-18 16:23                           ` Michael S. Tsirkin
2011-05-18 16:50                       ` Michael S. Tsirkin
2011-05-18 11:47                     ` Michał Mirosław
2011-05-18 11:56                       ` Michael S. Tsirkin
2011-05-18 12:48                         ` Michał Mirosław
2011-05-18 13:19                           ` Michael S. Tsirkin

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=20110516211459.GE18148@redhat.com \
    --to=mst@redhat.com \
    --cc=arnd@arndb.de \
    --cc=avi@redhat.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mashirle@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.