From: "Steve Wise" <swise@opengridcomputing.com>
To: "David Miller" <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH REPOST 1/2] Network Event Notifier Mechanism.
Date: Fri, 23 Jun 2006 21:27:19 -0500 [thread overview]
Message-ID: <001001c69735$b808e790$020010ac@haggard> (raw)
In-Reply-To: 20060623.135642.48528981.davem@davemloft.net
----- Original Message -----
From: "David Miller" <davem@davemloft.net>
To: <swise@opengridcomputing.com>
Cc: <netdev@vger.kernel.org>
Sent: Friday, June 23, 2006 3:56 PM
Subject: Re: [PATCH REPOST 1/2] Network Event Notifier Mechanism.
| From: Steve Wise <swise@opengridcomputing.com>
| Date: Fri, 23 Jun 2006 15:34:55 -0500
|
| > But what about the redirect event? It really needs to pass two bits
of
| > info: The old dst_entry ptr and the new dst_entry ptr. This is
needed
| > so the rdma driver can figure out which connections now need to use
the
| > new dst_entry...
|
| struct foo_event_data {
| struct whatever a;
| struct thistoo b;
| };
|
| struct foo_event_data x;
|
| x->a = xxx;
| x->b = yyy;
|
| event->data = (void *) &x;
| send_event(&event);
|
| Why do you need typed data to do this?
|
You don't. This is fine with me...
next prev parent reply other threads:[~2006-06-24 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 20:19 [PATCH REPOST 0/2][RFC] Network Event Notifier Mechanism Steve Wise
2006-06-23 20:19 ` [PATCH REPOST 1/2] " Steve Wise
2006-06-23 20:26 ` David Miller
2006-06-23 20:34 ` Steve Wise
2006-06-23 20:56 ` David Miller
2006-06-24 2:27 ` Steve Wise [this message]
2006-06-26 15:26 ` Steve Wise
2006-06-26 17:43 ` David Miller
2006-06-26 18:28 ` Steve Wise
2006-06-23 20:19 ` [PATCH REPOST 2/2] Core network changes to support network event notification Steve Wise
2006-06-27 12:50 ` [PATCH REPOST 0/2][RFC] Network Event Notifier Mechanism Herbert Xu
2006-06-27 14:31 ` Steve Wise
2006-06-27 22:32 ` Herbert Xu
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='001001c69735$b808e790$020010ac@haggard' \
--to=swise@opengridcomputing.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.