Lines Matching refs:seq_file

1 The seq_file interface
29 The seq_file interface is available via <linux/seq_file.h>. There are
30 three aspects to seq_file:
41 We'll look at the seq_file interface via an extremely simple example: a
69 Modules implementing a virtual file with seq_file must implement a simple
73 itself. A seq_file implementation that is formatting firewall rules, for
88 	static void *ct_seq_start(struct seq_file *s, loff_t *pos)
99 iterator, but that will not be the case for most other seq_file
103 For more complicated applications, the private field of the seq_file
117 	static void *ct_seq_next(struct seq_file *s, void *v, loff_t *pos)
128 	static void ct_seq_stop(struct seq_file *s, void *v)
136 	static int ct_seq_show(struct seq_file *s, void *v)
150 seq_file iterator is finished by creating a seq_operations structure with
165 the seq_file code. It can thus be anything that is useful in stepping
169 iterator function. However, the seq_file code (by design) will not sleep
171 is a reasonable thing to do. The seq_file code will also avoid taking any
177 The seq_file code manages positioning within the output created by the
179 output must be passed to the seq_file code. Some utility functions have
183 printk(), but which requires the seq_file pointer as an argument.
187 	seq_putc(struct seq_file *m, char c);
188 	seq_puts(struct seq_file *m, const char *s);
189 	seq_escape(struct seq_file *m, const char *s, const char *esc);
197 	int seq_path(struct seq_file *m, const struct path *path,
199 	int seq_path_root(struct seq_file *m, const struct path *path,
209 	bool seq_has_overflowed(struct seq_file *m);
212 A true return from seq_has_overflowed means that the seq_file buffer will
220 seq_file system, but we have not yet turned them into a file that a user
223 file. The seq_file interface provides a set of canned operations which do
236 On a successful open, seq_open() stores the struct seq_file pointer in
239 private field of the seq_file structure; that value can then be retrieved
244 private field of the seq_file structure, returning 0 on success. The
276 all implemented by the seq_file code itself. So a virtual file's
288 seq_file private field to kfree() before releasing the structure.
331 	                int (*show)(struct seq_file *m, void *p),
336 seq_file structure. When using single_open(), the programmer should use