StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhen transfer data from app to driver via IOCTL, which is better: by string or by common struct?
primarykey
Id
4182831
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-11-15T09:07:48.550
FavoriteCount
0
LastActivityDate
2010-11-15T09:33:21.600
LastEditDate
LastEditorUserId
0
OwnerUserId
188326
ParentId
0
PostTypeId
1
Score
0
ViewCount
318
LastEditorDisplayName
text
Body
If the app needs to exchange data with the underlying driver via IOCTL, I know that the app and the driver can define a common struct to hold data and pass it bidirectionally. However, I recently noticed that some app/driver doesn't use this paradigm. Instead, they pass a string represnetation of the data and let the driver parse the string to get each fileds of the data. I can feel that this is not a good choice, e.g. the string parser may slow the driver, which should be fast in kernel. Can anyone compare these two approaches and give the pros and cons? Thanks.
Tags
<driver><device-driver>
Title
When transfer data from app to driver via IOCTL, which is better: by string or by common struct?
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USsolotim
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
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.