[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <74c64ea31c51437eb718a94968809a0a@AMSPEX02CL03.citrite.net>
Date: Mon, 13 Feb 2017 14:19:10 +0000
From: Paul Durrant <Paul.Durrant@...rix.com>
To: 'Boris Ostrovsky' <boris.ostrovsky@...cle.com>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: Juergen Gross <jgross@...e.com>
Subject: RE: [PATCH v2 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP
> -----Original Message-----
> From: Boris Ostrovsky [mailto:boris.ostrovsky@...cle.com]
> Sent: 13 February 2017 14:09
> To: Paul Durrant <Paul.Durrant@...rix.com>; xen-devel@...ts.xenproject.org;
> linux-kernel@...r.kernel.org
> Cc: Juergen Gross <jgross@...e.com>
> Subject: Re: [PATCH v2 2/3] xen/privcmd: Add IOCTL_PRIVCMD_DM_OP
>
>
> >> How about something like (with rather arbitrary values)
> >>
> >> #define PRIVCMD_DMOP_MAX_NUM_BUFFERS 16
> >> #define PRIVCMD_DMOP_MAX_TOT_BUFFER_SZ 4096
> >>
> >> and make them part of the interface (i.e. put them into privcmd.h)?
> >
> > Given that the values are arbitrary, I think it may be better to make them
> module params. They can then at least be tweaked if privcmd becomes a
> problem with later dm_ops.
>
> Making them adjustable is a good thing but we still need default values.
>
Oh, sure. I think I'll actually go for 16 bufs and a max of 4k per bufs as defaults. Patch v3 (including a fix for the arm build) coming shortly.
Cheers,
Paul
>
> -boris
Powered by blists - more mailing lists