| To: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux |
| From: | Ivan Passos <lists@xxxxxxxxxxxx> |
| Date: | Tue, 5 Dec 2000 11:23:50 -0800 (PST) |
| Cc: | Linux Kernel List <linux-kernel@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx |
| In-reply-to: | <E143Ebi-000500-00@xxxxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
On Tue, 5 Dec 2000, Alan Cox wrote: > > I think a new ioctl would be sensible. There is a lot to go in it. Alan, what's the approach you'd feel more comfortable with: - One ioctl that passes a pointer to a known structure in ifr.ifr_data as its argument. - Several ioctl's, one for each parameter, that pass only the specific parameter new value as the argument. The former is good because it relies on a _single_ ioctl. However, every time you change the ioctl structure you may lose backward compatibility. The latter is good because new implementations / features won't affect previous working features. However, it'd create a huge list of ioctl's. Please let me know whatcha think. Later, Ivan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux, Ivan Passos |
|---|---|
| Next by Date: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux, Ivan Passos |
| Previous by Thread: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux, Robert Olsson |
| Next by Thread: | Re: [RFC-2] Configuring Synchronous Interfaces in Linux, Peter Samuelson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |