From: Greg KH <greg@kroah.com>
To: Alex Chiang <achiang@hp.com>, Matthew Wilcox <matthew@wil.cx>,
jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH, v2] PCI: create function symlinks in /sys/bus/pci/slots/N/
Date: Sat, 23 Aug 2008 08:44:50 -0700 [thread overview]
Message-ID: <20080823154450.GA27985@kroah.com> (raw)
In-Reply-To: <20080822195358.GC20820@ldl.fc.hp.com>
On Fri, Aug 22, 2008 at 01:53:58PM -0600, Alex Chiang wrote:
> * Matthew Wilcox <matthew@wil.cx>:
> > On Fri, Aug 22, 2008 at 10:20:49AM -0600, Alex Chiang wrote:
> > > This is a second attempt at creating some handy symlinks in
> > > /sys/bus/pci/ between slots and devices.
> > >
> > > It addresses the following concerns from last time:
> > >
> > > - does not create superfluous 'device' link
> > > - correctly adds and removes links after hotplug ops
> > > - adds a bunch of documentation ;)
> > >
> > > It does not address Willy's concerns about not needing the
> > > functionN back-links. I kinda thought they were useful, no one
> > > else seemed to express an opinion...
> >
> > I was just explaining why I didn't create them when I did my version of
> > this patch. I don't have an objection to adding them; they make logical
> > sense. The only concern might be the additional memory usage.
>
> Yes, agree about the memory usage, although I wonder what the
> actual overhead is.
>
> Does anyone have numbers for how much it costs to create a new
> symlink? I could try and figure this out but it will take a few
> days (busy with other stuff).
Almost nothing.
sysfs creates these things on the fly as they are accessed, and if
memory pressure on the machine happens, they are freed up properly and
then created again if a user asks to see them in the tree.
So don't worry about memory issues when adding new files or symlinks in
sysfs, it just isn't a problem (we handle 20000 disks easily on low
memory 31bit s390 systems.)
thanks,
greg k-h
next prev parent reply other threads:[~2008-08-23 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 16:20 [PATCH, v2] PCI: create function symlinks in /sys/bus/pci/slots/N/ Alex Chiang
2008-08-22 18:23 ` Matthew Wilcox
2008-08-22 19:53 ` Alex Chiang
2008-08-23 15:44 ` Greg KH [this message]
2008-08-23 20:04 ` Alex Chiang
2008-08-25 4:07 ` Greg KH
2008-08-27 3:50 ` Alex Chiang
2008-08-27 4:01 ` Greg KH
2008-08-27 14:21 ` Matthew Wilcox
2008-08-27 15:04 ` Greg KH
2008-08-27 22:44 ` Jesse Barnes
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=20080823154450.GA27985@kroah.com \
--to=greg@kroah.com \
--cc=achiang@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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