netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, NetDev <netdev@vger.kernel.org>
Subject: Re: How to grab a block of binary data w/out using ioctls?
Date: Tue, 24 Oct 2006 19:25:48 -0700	[thread overview]
Message-ID: <453ECB2C.3070202@candelatech.com> (raw)
In-Reply-To: <20061024050014.GC12506@havoc.gtf.org>

Jeff Garzik wrote:
> On Mon, Oct 23, 2006 at 09:54:48PM -0700, Randy Dunlap wrote:
>   
>> Similarly, sysfs is desirable in some circumstances, but
>> not for blocks of binary data.
>>     
>
> sysfs specifically has APIs for binary data...
>   
 From reading the Documentation/filesystems/sysfs.txt, it seems like
it is not recommended that one use sysfs for anything other than
very simple (and single) attributes.

If you know of a piece of code that actually passes back a struct or
other binary blob of data, please point me to it so I can learn from it.

Thanks,
Ben

> 	Jeff
>
>
>   


-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com



  parent reply	other threads:[~2006-10-25  2:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24  0:44 How to grab a block of binary data w/out using ioctls? Ben Greear
2006-10-24  4:54 ` Randy Dunlap
2006-10-24  5:00   ` Jeff Garzik
2006-10-24  5:04     ` Randy.Dunlap
2006-10-25  2:25     ` Ben Greear [this message]
2006-10-25  2:47       ` Jeff Garzik
2006-10-25  4:35         ` Randy Dunlap
2006-10-25  4:46           ` Jeff Garzik
2006-10-25  4:52             ` Randy.Dunlap
2006-10-25  5:01               ` Jeff Garzik
2006-10-25  5:07                 ` Randy.Dunlap
2006-10-25 16:30             ` Ben Greear
2006-10-25 12:51 ` Hagen Paul Pfeifer

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=453ECB2C.3070202@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.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).