Re: removing tq_name [Was: taskqueue_create() name parameter lieftime]

2010-11-23 Thread Andriy Gapon
on 22/11/2010 16:30 John Baldwin said the following: No. Especially since the structure is private it can always be revived if a use is found for it. You can probably leave the taskqueue_create() API the same for now though. OK. Committed. Thank you! -- Andriy Gapon

Re: removing tq_name [Was: taskqueue_create() name parameter lieftime]

2010-11-22 Thread John Baldwin
On Saturday, November 20, 2010 5:00:34 am Andriy Gapon wrote: on 19/11/2010 18:58 John Baldwin said the following: On Friday, November 19, 2010 11:20:04 am Andriy Gapon wrote: BTW, tq_name doesn't seem to be used anywhere at all. Perhaps just drop it? But still could be useful in a

removing tq_name [Was: taskqueue_create() name parameter lieftime]

2010-11-20 Thread Andriy Gapon
on 19/11/2010 18:58 John Baldwin said the following: On Friday, November 19, 2010 11:20:04 am Andriy Gapon wrote: BTW, tq_name doesn't seem to be used anywhere at all. Perhaps just drop it? But still could be useful in a debugger, though. If it's not used anywhere I would just drop it.

Re: taskqueue_create() name parameter lieftime

2010-11-19 Thread Andriy Gapon
on 16/11/2010 15:27 John Baldwin said the following: On Tuesday, November 16, 2010 7:20:47 am Andriy Gapon wrote: taskqueue_create() documentation never explicitly says this, but current taskqueue_create() implementation just stores a 'name' pointer parameter internally. Thus it depends on

Re: taskqueue_create() name parameter lieftime

2010-11-19 Thread John Baldwin
On Friday, November 19, 2010 11:20:04 am Andriy Gapon wrote: on 16/11/2010 15:27 John Baldwin said the following: On Tuesday, November 16, 2010 7:20:47 am Andriy Gapon wrote: taskqueue_create() documentation never explicitly says this, but current taskqueue_create() implementation just

taskqueue_create() name parameter lieftime

2010-11-16 Thread Andriy Gapon
taskqueue_create() documentation never explicitly says this, but current taskqueue_create() implementation just stores a 'name' pointer parameter internally. Thus it depends on the 'name' having a life time encompassing that of the taskqueue. I think that alternatively we could have copied the

Re: taskqueue_create() name parameter lieftime

2010-11-16 Thread John Baldwin
On Tuesday, November 16, 2010 7:20:47 am Andriy Gapon wrote: taskqueue_create() documentation never explicitly says this, but current taskqueue_create() implementation just stores a 'name' pointer parameter internally. Thus it depends on the 'name' having a life time encompassing that of

Re: taskqueue_create() name parameter lieftime

2010-11-16 Thread Pawel Jakub Dawidek
On Tue, Nov 16, 2010 at 08:27:11AM -0500, John Baldwin wrote: On Tuesday, November 16, 2010 7:20:47 am Andriy Gapon wrote: taskqueue_create() documentation never explicitly says this, but current taskqueue_create() implementation just stores a 'name' pointer parameter internally. Thus