From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>,
devel@openvz.org
Subject: Re: [PATCH 2/6][INET]: Consolidate inet(6)_hash_connect.
Date: Thu, 31 Jan 2008 11:39:55 -0200 [thread overview]
Message-ID: <20080131133954.GU1819@ghostprotocols.net> (raw)
In-Reply-To: <47A1CABB.8050805@openvz.org>
Em Thu, Jan 31, 2008 at 04:18:51PM +0300, Pavel Emelyanov escreveu:
> Arnaldo Carvalho de Melo wrote:
> > Em Thu, Jan 31, 2008 at 03:32:09PM +0300, Pavel Emelyanov escreveu:
> >> These two functions are the same except for what they call
> >> to "check_established" and "hash" for a socket.
> >>
> >> This saves half-a-kilo for ipv4 and ipv6.
> >
> > Good stuff!
> >
> > Yesterday I was perusing tcp_hash and I think we could have the hashinfo
> > pointer stored perhaps in sk->sk_prot.
> >
> > That way we would be able to kill tcp_hash(), inet_put_port() could
> > receive just sk, etc.
>
> But each proto will still have its own hashfn, so proto's
> callbacks will be called to hash/unhash sockets, so this will
> give us just one extra dereference. No?
>
> > What do you think?
>
> Hmmm... Even raw_hash, etc may become simpler. On the other hand
> maybe this is a good idea, but I'm not very common with this code
> yet to foresee such things in advance... I think that we should
> try to prepare a patch and look, but if you have smth ready, then
> it's better to review your stuff first.
gimme some minutes
- Arnaldo
next prev parent reply other threads:[~2008-01-31 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 12:32 [PATCH 2/6][INET]: Consolidate inet(6)_hash_connect Pavel Emelyanov
2008-01-31 13:01 ` Arnaldo Carvalho de Melo
2008-01-31 13:15 ` David Miller
2008-01-31 13:18 ` Pavel Emelyanov
2008-01-31 13:39 ` Arnaldo Carvalho de Melo [this message]
2008-01-31 15:42 ` Arnaldo Carvalho de Melo
2008-01-31 13:04 ` David Miller
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=20080131133954.GU1819@ghostprotocols.net \
--to=acme@redhat.com \
--cc=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).