da...@l8s.co.uk (David Laight) writes:
>But what tends to happen is that the disk 'elevator' algorithm makes
>one of the server process wait ages for its disk access to complete,
>by which time the client has timed out and resubmitted the RPC request.
The NFS client does not resubmit the RPC requ
Lourival Vieira Neto wrote:
> Hi Folks,
>
> Here is a patch that puts ptrdiff_t in the kernel. It also creates a
> sys/stddef.h header.
Why sys/stddef.h? Just keep them in sys/types.h please.
--
Mindaugas
On Tue, Nov 19, 2013 at 04:02:51PM +0100, Christoph Badura wrote:
> After updating my -current kernel from 6.99.24 to 6.99.27 so I could
> commit my ubsec(4) changes I noticed that under 6.99.27 I get between
> 3 and 8 percent less throughput on accelerated crypto ops.
I was able to pin this down
On Mon, Dec 02, 2013 at 08:33:38PM +0100, Marc Balmer wrote:
> Some Illumos developers consider adding Lua to the kernel to provide
> what they call ZFS Channel Programs:
>
> http://www.youtube.com/watch?v=EGKek5sZ2Xw&list=PLaUVvul17xSdWMBt5tAC8Hu7bbeWskD_q
>
> Lua part starts at approx 1:13
Real
Hi Mindaugas,
>> Here is a patch that puts ptrdiff_t in the kernel. It also creates a
>> sys/stddef.h header.
>
> Why sys/stddef.h? Just keep them in sys/types.h please.
To avoid redefining ptrdiff_t on stddef.h. I think it would be more
coherent, since ptrdiff_t is a stddef.h definition and std
Is there a reason to do not have ptrdiff_t defined in the kernel?
Shouldn't be OK to define it in sys/cdefs.h? Or even for having
stddef.h itself in the kernel?
>>>
>>> It is defined in the kernel and comes from via
>>> .
>>
>> Actually, it isn't. Only _BSD_PTRDIFF_T_ is defined by
On Wed, Dec 04, 2013 at 12:04:23PM -0200, Lourival Vieira Neto wrote:
> Hi Mindaugas,
>
> >> Here is a patch that puts ptrdiff_t in the kernel. It also creates a
> >> sys/stddef.h header.
> >
> > Why sys/stddef.h? Just keep them in sys/types.h please.
>
> To avoid redefining ptrdiff_t on stddef.
Hi Joerg,
On Wed, Dec 4, 2013 at 12:25 PM, Joerg Sonnenberger
wrote:
> On Wed, Dec 04, 2013 at 12:04:23PM -0200, Lourival Vieira Neto wrote:
>> Hi Mindaugas,
>>
>> >> Here is a patch that puts ptrdiff_t in the kernel. It also creates a
>> >> sys/stddef.h header.
>> >
>> > Why sys/stddef.h? Just
On Wed, Dec 04, 2013 at 12:07:42PM -0200, Lourival Vieira Neto wrote:
> >>> No, is not allowed in the kernel. Symbols from it are
> >>> provided via other means.
> >>
> >> I know. In fact, I'm asking if it would be alright to allow that.
> >> AFAIK, it would be inoffensive if available in the ker
On Wed, Dec 04, 2013 at 10:13:14AM -0600, David Young wrote:
> I would prefer for this to suffice both for the kernel and userland:
>
> #include /* for bool */
> #include /* for size_t */
>
> ISTM that the reasons things are not that simple are merely historical
> reasons,
On Wed, Dec 04, 2013 at 01:54:56PM -0200, Lourival Vieira Neto wrote:
> >> > Why sys/stddef.h? Just keep them in sys/types.h please.
> >>
> >> To avoid redefining ptrdiff_t on stddef.h. I think it would be more
> >> coherent, since ptrdiff_t is a stddef.h definition and stddef.h
> >> shouldn'
On Wed, Dec 04, 2013 at 02:09:49PM +0100, Christoph Badura wrote:
> I was able to pin this down on the pcu/fpu changes. A kernel from just
> before that change doesn't have the performance loss.
Those have been reverted.
Thomas
On Wed, 04 Dec 2013, David Holland wrote:
(*) A complete scheme for doing it right removes all the _BSD_FOO_T_
drivel and ifdefs scattered in userland headers in favor of:
- a single header file that defines all the needed types prefixed
with __, which can be included anywhere;
- in userl
On Dec 4, 2013, at 1:33 PM, Alan Barrett wrote:
> On Wed, 04 Dec 2013, David Holland wrote:
>> (*) A complete scheme for doing it right removes all the _BSD_FOO_T_
>> drivel and ifdefs scattered in userland headers in favor of:
>> - a single header file that defines all the needed types prefixe
Hi David, Alan and Matt,
On Wed, Dec 4, 2013 at 7:38 PM, Matt Thomas wrote:
>
> On Dec 4, 2013, at 1:33 PM, Alan Barrett wrote:
>
>> On Wed, 04 Dec 2013, David Holland wrote:
>>> (*) A complete scheme for doing it right removes all the _BSD_FOO_T_
>>> drivel and ifdefs scattered in userland head
dyo...@pobox.com (David Young) writes:
>I would prefer for this to suffice both for the kernel and userland:
> #include /* for bool */
> #include /* for size_t */
I bet that most places would need something like:
#include
#include
#if defined(_KERNEL) || defined(_STANDALON
16 matches
Mail list logo