Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- From: David Miller <davem@xxxxxxxxxxxxx>
- Date: Wed, 14 Nov 2007 03:52:36 -0800 (PST)
From: Paul Mackerras <paulus@xxxxxxxxx>
Date: Wed, 14 Nov 2007 22:44:56 +1100
For instance, if you have something that kind-of looks like
read_pmds(int n, int *pmd_numbers, u64 *pmd_values);
where the caller supplies an array of PMD numbers and the function
returns their values (and you want that reading to be done atomically
in some sense), how would you do that using special files and fops?
The same way we handle some of the multicast "getsockopt()"
calls. The parameters passed in are both inputs and outputs.
For the above example:
struct pmd_info {
int *pmd_numbers;
u64 *pmd_values;
int n;
} *p;
buffer_size = N;
p = malloc(buffer_size);
p->pmd_numbers = p + foo;
p->pmd_values = p + bar;
p->n = whatever(N);
err = read(fd, p, N);
It's definitely doable, use your imagination.
You can encode all kinds of operation types into the
header as well.
Another alternative is to use generic netlink.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- From: Paul Mackerras
- Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- References:
- Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- From: Christoph Hellwig
- Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- From: David Miller
- Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- From: Paul Mackerras
- Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- Prev by Date: Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- Next by Date: Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- Previous by thread: Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- Next by thread: Re: [perfmon] Re: [perfmon2] perfmon2 merge news
- Index(es):
Relevant Pages
|