Re: TUNABLE_INT question

2009-02-18 Thread Roman Divacky
On Tue, Feb 17, 2009 at 05:51:13PM -0500, John Baldwin wrote: On Tuesday 17 February 2009 5:21:42 pm Roman Divacky wrote: On Tue, Feb 17, 2009 at 09:31:12AM -0500, John Baldwin wrote: On Friday 13 February 2009 5:16:07 pm Roman Divacky wrote: On Fri, Feb 13, 2009 at 03:55:44PM -0500,

Re: TUNABLE_INT question

2009-02-17 Thread John Baldwin
On Friday 13 February 2009 5:16:07 pm Roman Divacky wrote: On Fri, Feb 13, 2009 at 03:55:44PM -0500, Ryan Stone wrote: __FILE__ is a string so you can't concat that with anything to produce an identifier. In any case, the variable is static so there can't be any collision problems with

Re: TUNABLE_INT question

2009-02-17 Thread John Baldwin
On Tuesday 17 February 2009 5:21:42 pm Roman Divacky wrote: On Tue, Feb 17, 2009 at 09:31:12AM -0500, John Baldwin wrote: On Friday 13 February 2009 5:16:07 pm Roman Divacky wrote: On Fri, Feb 13, 2009 at 03:55:44PM -0500, Ryan Stone wrote: __FILE__ is a string so you can't concat that

TUNABLE_INT question

2009-02-13 Thread Roman Divacky
hi #define TUNABLE_INT(path, var) \ static struct tunable_int __CONCAT(__tunable_int_, __LINE__) = { \ (path), \ (var), \ };

Re: TUNABLE_INT question

2009-02-13 Thread Ryan Stone
__FILE__ is a string so you can't concat that with anything to produce an identifier. In any case, the variable is static so there can't be any collision problems with other files. Ryan Stone ___ freebsd-hackers@freebsd.org mailing list

Re: TUNABLE_INT question

2009-02-13 Thread Roman Divacky
On Fri, Feb 13, 2009 at 03:55:44PM -0500, Ryan Stone wrote: __FILE__ is a string so you can't concat that with anything to produce an identifier. In any case, the variable is static so there can't be any collision problems with other files. I was talking about the SYSINIT parameter. thats a