From: Jean Tourrilhes <jt@hpl.hp.com>
To: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Cc: "David S. Miller" <davem@davemloft.net>,
irda-users@lists.sourceforge.net, netdev@oss.sgi.com,
Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [PATCH 6/9] irda: use sock slab cache
Date: Wed, 19 Jan 2005 18:16:07 -0800 [thread overview]
Message-ID: <20050120021607.GA11216@bougret.hpl.hp.com> (raw)
In-Reply-To: <41EF11AF.70203@conectiva.com.br>
On Thu, Jan 20, 2005 at 12:04:31AM -0200, Arnaldo Carvalho de Melo wrote:
> Hi David, Jean,
>
> Please read the log in the patch.
>
> Regards,
>
> - Arnaldo
>
> ===================================================================
>
>
> ChangeSet@1.2342, 2005-01-19 23:04:52-02:00, acme@toy.ghostprotocols.net
> [IRDA] use a private slab cache for socks
>
> Required to get rid of sk_protinfo and to introduce struct connection_sock,
> also for consistency with other protocol families implementations.
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 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
(except here, of course).
Thanks, and have fun...
Jean
next prev parent reply other threads:[~2005-01-20 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 2:04 [PATCH 6/9] irda: use sock slab cache Arnaldo Carvalho de Melo
2005-01-20 2:16 ` Jean Tourrilhes [this message]
2005-01-20 3:47 ` Arnaldo Carvalho de Melo
2005-01-20 8:54 ` Christoph Hellwig
2005-01-20 14:55 ` Arnaldo Carvalho de Melo
2005-01-20 15:20 ` Arnaldo Carvalho de Melo
2005-01-20 17:25 ` Jean Tourrilhes
2005-01-20 21:08 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050120021607.GA11216@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=acme@conectiva.com.br \
--cc=davem@davemloft.net \
--cc=irda-users@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.