Re: [PATCH v2 01/15] net: proc entry showing inodes on sockfs and their types

> > Sorry, you cannot do this. > > You are adding a new lock and insert into a global list for > pretty much every socket created, that will destroy performance. I think there are no serious performance penalty in generally use. Most frequently used types of sockets like tcp, udp, and unix are n

Re: [PATCH v2 01/15] net: proc entry showing inodes on sockfs and their types

I also want to mention that I absolutely do not consider better lsof support important at all. So if you want to add this, it had to be exactly zero overhead and it must not break anything that exists already. Your patch set violates this on both counts. -- To unsubscribe from this list: send th

Re: [PATCH v2 01/15] net: proc entry showing inodes on sockfs and their types

Sorry, you cannot do this. You are adding a new lock and insert into a global list for pretty much every socket created, that will destroy performance. You also cannnot add new fields to socket listing procfs files, it will break existing application which depend upon the existing exact layout o

[PATCH v2 01/15] net: proc entry showing inodes on sockfs and their types

I've worked on improving lsof output on linux both lsof and linux sides. Sometimes lsof cannot resolve socket descriptors and as the result it prints them like: [yamato@localhost]/tmp% sudo lsof | grep dbus | grep iden dbus-daem 652 dbus6u sock ... 17812 can't identify