Sridhar Samudrala <[EMAIL PROTECTED]> wrote:
>>
>> What about using the same fields (rqueue/wqueue) as you did for /proc?
>
> I meant extending tcp_info structure to add new fields. I think the user
> space also uses this structure.
What about putting it into inet_idiag_msg.idiag_[rw]queue inste
On Thu, 2006-06-22 at 10:21 +1000, Herbert Xu wrote:
> Sridhar Samudrala <[EMAIL PROTECTED]> wrote:
> >
> > In order to support this with netstat/ss that use netlink mechanism to
> > get the socket info, i think we need to extend tcp_info to add this field.
> > Can this be done in a backward compa
Sridhar Samudrala <[EMAIL PROTECTED]> wrote:
>
> In order to support this with netstat/ss that use netlink mechanism to
> get the socket info, i think we need to extend tcp_info to add this field.
> Can this be done in a backward compatible way?
What about using the same fields (rqueue/wqueue) as
While debugging a TCP server hang issue, we noticed that currently there is
no way for a user to find the acceptq backlog value for a TCP listen socket.
All the standard networking utilities that display socket info like netstat,
ss and /proc/net/tcp have 2 fields called rx_queue and tx_queue. I