From: Stephen Hemminger <shemminger@vyatta.com>
To: "Kiran Kotla" <kotlakiran@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: setting ICSK_CA_PRIV_SIZE larger than 16 * sizeof(u32)
Date: Fri, 27 Jun 2008 14:32:58 -0700 [thread overview]
Message-ID: <20080627143258.173120cd@extreme> (raw)
In-Reply-To: <965f530d0806271420y7ffebd40xb9b2f9a035206932@mail.gmail.com>
On Fri, 27 Jun 2008 16:20:10 -0500
"Kiran Kotla" <kotlakiran@gmail.com> wrote:
> Hi david,
>
> Thank you very much for your response. I am new to this forum and not
> sure if I could include you in my reply.
>
> Well, we tried our best to reduce the size of our private variables.
>
> The major consumers of space however are two arrays of 32 bit integers
> each of size '8', which are used to estimate drop probability and
> early congestion response probability (our protocol specific), which
> cannot be reduced to be 16 bit integers and further the size of the
> array cannot be reduced to some value lesser without degrading the
> estimation of drop probability.
>
> I guess the only way left is to have a trade-off between the
> performance of our protocol and size of the array.
>
> In any case, I was wondering if still there is a way to increase the
> size of the blob, though we would not to increase the size of blob to
> get our protocol running in the kernel.
>
> Thanks again!
> Kiran
If need be you can use a pointer to an allocated array for that (it would be
up to your code to free it). You might even want to make this per route
rather than per socket. That would require lookup/locking/ref counting, but
it would allow sharing path information when multiple sockets along same
path are present.
prev parent reply other threads:[~2008-06-27 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <965f530d0806270137y19c36638yc6ae0a1d4bfa63e7@mail.gmail.com>
2008-06-27 9:30 ` setting ICSK_CA_PRIV_SIZE larger than 16 * sizeof(u32) David Miller
2008-06-27 21:20 ` Kiran Kotla
2008-06-27 21:32 ` Stephen Hemminger [this message]
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=20080627143258.173120cd@extreme \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=kotlakiran@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).