[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111117162955.GA6758@phenom.dumpdata.com>
Date: Thu, 17 Nov 2011 11:29:56 -0500
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: annie li <annie.li@...cle.com>
Cc: Ian Campbell <Ian.Campbell@...rix.com>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jeremy@...p.org" <jeremy@...p.org>,
"kurt.hackel@...cle.com" <kurt.hackel@...cle.com>,
Paul Durrant <Paul.Durrant@...rix.com>
Subject: Re: [PATCH 1/3] xen/granttable: Introducing grant table V2 stucture
> >The more normal way to do this would be to make gnttab_interface a
> >pointer, define gnttab_v1_ops and do:
> > gnttab_interface = &gnttab_v1_ops;
> >or if the pointer overhead is significant remove that and just do a
> >struct assignment:
> > gnttab_interface = gnttab_v1_ops;
> >
> If using this way, we need two more public structures(gnttab_v1_ops
> and gnttab_v2_ops), and two more functions to initialize those two
> structures and then initialize the pointer gnttab_interface. It is
> more complicated, am i missing something?
Why two functions? I agree on the structures - but they need not to be
public (they can be static).
For a good example look at how apic_physflat is done.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists