StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19554155
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-23T17:23:15.463
FavoriteCount
0
LastActivityDate
2013-10-23T17:29:23.187
LastEditDate
LastEditorUserId
0
OwnerUserId
1151724
ParentId
19554154
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
If by sysfs you mean the <code>sysfs()</code> library call, notice this in <code>man 2 sysfs</code>: <blockquote> NOTES This System-V derived system call is obsolete; don't use it. On systems with /proc, the same information can be obtained via /proc/filesystems; use that interface instead. </blockquote> I can't recall noticing stuff that had an <code>ioctl()</code> and a sysfs interface, but probably they exist. I'd use the proc or sys handle anyway, since that tends to be less cryptic and more flexible. If by sysfs you mean accessing files in <code>/sys</code>, that's the preferred method. <blockquote> I'm looking for generic info, such as "ioctl is faster because you've removed the file layer from the function calls". </blockquote> Accessing procfs or sysfs files does not entail an I/O bottleneck because they are not real files -- they are kernel interfaces. So no, accessing this stuff through "the file layer" does not affect performance. This is a not uncommon misconception in linux systems programming, I think. Programmers can be squeamish about system calls that aren't well, system calls, and paranoid that opening a file will be somehow slower. Of course, file I/O in the ABI is just system calls anyway. What makes a normal (disk) file read slow is not the calls to open, read, write, whatever, it's the hardware bottleneck. I always use low level descriptor based functions (<code>open()</code>, <code>read()</code>) instead of high level streams when doing this because at some point some experience led me to believe they were more reliable for this specifically (reading from <code>/proc</code>). I can't say whether that's definitively true. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIn general, on ucLinux, is ioctl faster than writing to /sys filesystem?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USdelicateLatticeworkFever
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.