kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: xerofoify@gmail.com (nick)
To: kernelnewbies@lists.kernelnewbies.org
Subject: VFS/driver core overhead
Date: Mon, 06 Apr 2015 23:12:34 -0400	[thread overview]
Message-ID: <55234B22.9010804@gmail.com> (raw)

Greetings All,
After reading through the code for the usb and vfs core infrastructure, I was wondering if 
after reading it if I am correct in my notion of there being very little overhead or none
at all int these areas of the kernel. This is due to be noticing most drivers and file 
systems wrap around the core/vfs and therefore the overhead is very little and no need
to worry about it like the overhead of the kernel's process structures based off task_struct
.Honestly, I could benchmark this area of the kernel but it's hard to remove the file 
system/drivers interfering with my benchmarks due to me not knowing of any one way to do that.
If someone either points me to a benchmark for me to test this or answers it that would be
very helpful.
Thanks,
Nick

             reply	other threads:[~2015-04-07  3:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07  3:12 nick [this message]
2015-04-07 14:56 ` VFS/driver core overhead Valdis.Kletnieks at vt.edu

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=55234B22.9010804@gmail.com \
    --to=xerofoify@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).