Author: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2005 00:04:31 -0200
Hi David, Jean, Please read the log in the patch. Regards, - Arnaldo == ChangeSet@xxxxxx, 2005-01-19 23:04:52-02:00, acme@xxxxxxxxxxxxxxxxxxxxxx [IRDA] use a private slab cache for socks Required to
I don't have anything against this patch, as it looks clean and straightforward. Stephen might have something to say. I'm way behind, so it may take a while before I test that. I'm just curious about
Author: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2005 01:47:10 -0200
Jean Tourrilhes escreveu: I'm just curious about the overhead of adding a specific slab for IrDA sockets. Most users never create any (using IrCOMM), or maximum one (using Obex), so it's not like it
But as Jean sais this type of socket is used very little, as are a few other probably (raw, pfkey?), so maybe those should just use kmalloc + kfree instead of their own slab?
Author: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2005 12:55:45 -0200
I'm just curious about the overhead of adding a specific slab for IrDA sockets. Most users never create any (using IrCOMM), or maximum one (using Obex), so it's not like it will get a lot of use (ex
Author: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2005 13:20:49 -0200
Arnaldo Carvalho de Melo escreveu: Christoph Hellwig escreveu: I'm just curious about the overhead of adding a specific slab for IrDA sockets. Most users never create any (using IrCOMM), or maximum o
Just to clarify, but I think you already got this nuance. I was not talking about the frequency of people using IrDA. I just say that when people use IrDA, they are likely to use few sockets (as oppo
Author: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2005 19:08:06 -0200
stage should be, the protocols will just use (IRDA for the example): Can't we just transition IrDA sockets to "future", rather than "transitional". This way we are done, and no longer need to worry