| To: | "open-iscsi@xxxxxxxxxxxxxxxx" <open-iscsi@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics |
| From: | Dmitry Yusupov <dmitry_yus@xxxxxxxxx> |
| Date: | Sun, 27 Mar 2005 10:47:07 -0800 |
| Cc: | mpm@xxxxxxxxxxx, andrea@xxxxxxx, James.Bottomley@xxxxxxxxxxxxxxxxxxxxx, ksummit-2005-discuss@xxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <4246FAD5.5080700@cs.wisc.edu> |
| References: | <4241D106.8050302@cs.wisc.edu> <20050324101622S.fujita.tomonori@lab.ntt.co.jp> <1111628393.1548.307.camel@beastie> <20050324113312W.fujita.tomonori@lab.ntt.co.jp> <1111633846.1548.318.camel@beastie> <20050324215922.GT14202@opteron.random> <424346FE.20704@cs.wisc.edu> <20050324233921.GZ14202@opteron.random> <20050325034341.GV32638@waste.org> <20050327035149.GD4053@g5.random> <20050327054831.GA15453@waste.org> <1111905181.4753.15.camel@mylaptop> <20050326224621.61f6d917.davem@davemloft.net> <1111907130.4753.32.camel@mylaptop> <20050326235712.25f9ca36.davem@davemloft.net> <1111911493.5824.12.camel@mylaptop> <4246FAD5.5080700@cs.wisc.edu> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Sun, 2005-03-27 at 10:26 -0800, Mike Christie wrote: > Dmitry Yusupov wrote: > > On Sat, 2005-03-26 at 23:57 -0800, David S. Miller wrote: > > > >>On Sat, 26 Mar 2005 23:05:30 -0800 > >>Dmitry Yusupov <dmitry_yus@xxxxxxxxx> wrote: > >> > >> > >>>>During these gaps in time, you will need to keep your HW receive > >>>>ring populated with packets. > >>> > >>>ethernet flow-control must take care this case. > >>> > >>>If driver's replenish logic could mix alloc_skb/netif_rx and SKB > >>>recycling than pause frames should never happen even with gige+ > >>>interfaces. > >> > >>I don't see what the big deal is if pause frames > >>are generated when the system is low on atomic memory > >>and RX allocations thus fail. > > > > > > not a big deal may be. but. very interesting case when OOM causing > > paging in/out and swapping device are on the same network under iSCSI > > control. (disk-less setups) having reliable receive in that case is > > important for making progress for READ operations. > > reliable receive is ciritical for WRITEs. Even if the WRITE is executed > successfully on the remote device, if we cannot receive the return status > from the device the operation will fail at the iscsi driver side due to a > SCSI timeout. of course. forget to mention this at the first place. WRITE needs successful SCSI response too. until that it will not be returned back to the SCSI Mid-Layer. |
| Previous by Date: | Re: IMQ again WAS(Re: iptables breakage WAS(Re: dummy as IMQ replacement, Andy Furniss |
|---|---|
| Next by Date: | Re: Resend: Re: PATCH: IPSEC acquire in presence of multiple managers, jamal |
| Previous by Thread: | Re: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics, Dmitry Yusupov |
| Next by Thread: | RE: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics, Alex Aizman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |