From: Andi Kleen <andi@firstfloor.org>
To: "Ian Brown" <ianbrn@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] UDP SndbufErrors interface and the /proc/net/udp interface.
Date: Tue, 01 Jul 2008 12:18:45 +0200 [thread overview]
Message-ID: <87wsk5ucu2.fsf@basil.nowhere.org> (raw)
In-Reply-To: <d0383f90806302347q702416faxe29901bf0d2cdbbb@mail.gmail.com> (Ian Brown's message of "Tue, 1 Jul 2008 09:47:23 +0300")
"Ian Brown" <ianbrn@gmail.com> writes:
>
> I wonder: would such a patch (form me or others) in needed ? Or will
> it be rejected because this idea is not good ?
> In case this idea is not good, I wonder what is the reason for it.
One possible reason against it is that struct sock size is relatively
critical for memory consumption and there's usually some resistance
against adding more fields for it.
That might be overriden by a very clear use case.
-Andi
next prev parent reply other threads:[~2008-07-01 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 6:47 [RFC] UDP SndbufErrors interface and the /proc/net/udp interface Ian Brown
2008-07-01 10:18 ` Andi Kleen [this message]
2008-07-01 13:50 ` Ian Brown
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=87wsk5ucu2.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=ianbrn@gmail.com \
--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).