netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: "Rémi Denis-Courmont" <remi.denis-courmont@nokia.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] Phonet: sockets list through proc_fs
Date: Mon, 20 Jul 2009 15:00:40 +0200	[thread overview]
Message-ID: <1248094840.4549.119.camel@violet> (raw)
In-Reply-To: <200907201549.30870.remi.denis-courmont@nokia.com>

Hi Remi,

> > > > On Monday 20 July 2009 13:21:01 ext Marcel Holtmann wrote:
> > > >> > It's just like most network protocols exposing their sockets list in
> > > >> > /proc/net. Debugging/monitoring indeed.
> > > >>
> > > >> I think that for new protocols, we should not do this anymore and just
> > > >> use debugfs. Since that is exactly its job.
> > > >
> > > > Requiring debugfs for something like 'netstat' sounds restrictive to
> > > > me...
> > >
> > > Me too.
> >
> > hold on, what has netstat to do with Phonet support?
> 
> First, I said "*like* netstat". Second, *net*stat has at least as much to do 
> with Pho*net* than it has with Unix sockets. I'm interested in monitoring 
> userland usage of Phonet sockets, not so much in debugging the kernel-mode 
> Phonet stack. I am not convinced that debugfs is the right tool at all here - 
> regardless whether we extend netstat or write a Phonet-specific tool.

in the end it is up to Dave, however I would put these things into
debugfs. Note that even something like mac80211 still provides a
wireless file here while most debugging is nowaydays in debugfs and it
might be better removed.

Regards

Marcel



  reply	other threads:[~2009-07-20 13:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  8:34 [PATCH] Phonet: sockets list through proc_fs Rémi Denis-Courmont
2009-07-20  8:36 ` Marcel Holtmann
2009-07-20  9:28   ` Rémi Denis-Courmont
2009-07-20  9:34     ` Marcel Holtmann
2009-07-20  9:47       ` Rémi Denis-Courmont
2009-07-20 10:21         ` Marcel Holtmann
2009-07-20 10:31           ` Eric Dumazet
2009-08-03  2:42             ` Arnaldo Carvalho de Melo
2009-07-20 10:32           ` Rémi Denis-Courmont
2009-07-20 10:43             ` David Miller
2009-07-20 12:07               ` Marcel Holtmann
2009-07-20 12:49                 ` Rémi Denis-Courmont
2009-07-20 13:00                   ` Marcel Holtmann [this message]
2009-07-20 14:09                     ` David Miller
2009-07-20 14:25                       ` Marcel Holtmann
2009-07-20 14:05                 ` David Miller
2009-07-20  9:05 ` Eric Dumazet
  -- strict thread matches above, loose matches on Subject: below --
2009-07-21 11:57 Rémi Denis-Courmont
2009-07-21 19:34 ` David Miller
2009-08-12 11:02   ` Rémi Denis-Courmont
2009-08-12 18:06     ` 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=1248094840.4549.119.camel@violet \
    --to=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=remi.denis-courmont@nokia.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 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).