All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: marcel@holtmann.org, davem@davemloft.net, netdev@oss.sgi.com
Subject: Re: [PATCH][BLUETOOTH] kill bt_sock_alloc
Date: Wed, 9 Mar 2005 14:43:54 -0300	[thread overview]
Message-ID: <39e6f6c7050309094379d155e@mail.gmail.com> (raw)
In-Reply-To: <422F33E9.4030401@qualcomm.com>

On Wed, 09 Mar 2005 09:35:37 -0800, Max Krasnyansky <maxk@qualcomm.com> wrote:
> Arnaldo Carvalho de Melo wrote:
> > Em Tue, Mar 08, 2005 at 06:49:37AM -0300, Arnaldo Carvalho de Melo escreveu:
> >
> >>Hi,
> >>
> >>      Please take a look and if acceptable pull from:
> >>
> >>bk://kernel.bkbits.net/acme/connection_sock-2.6
> >
> >
> > Sorry, now with the patch attached.
> 
> Looks good to me. Marcel I'd suggest for you to apply this patch.
> It helps in reducing overall size of the socket structures.

Please note that there are further space savings to tap into in the bt_sock
class hierarchy, as not all of the bt_sock descendants  needs things like
bt_sock::accept_q,  etc

And when the "kill sk_protinfo" series is finished, there will be further space
savings, as the same bt_sock descendants that don't use accept_q will not
need to have struct connection_sock in its definition.

-- 
- Arnaldo

  reply	other threads:[~2005-03-09 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08  9:49 [PATCH][BLUETOOTH] kill bt_sock_alloc Arnaldo Carvalho de Melo
2005-03-08  9:52 ` Arnaldo Carvalho de Melo
2005-03-09 17:35   ` Max Krasnyansky
2005-03-09 17:43     ` Arnaldo Carvalho de Melo [this message]
2005-03-09 18:24     ` Marcel Holtmann
2005-03-09 18:43       ` Arnaldo Carvalho de Melo
2005-03-10 19:51         ` Marcel Holtmann

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=39e6f6c7050309094379d155e@mail.gmail.com \
    --to=arnaldo.melo@gmail.com \
    --cc=acme@conectiva.com.br \
    --cc=davem@davemloft.net \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.com \
    --cc=netdev@oss.sgi.com \
    /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.